Uncaught TypeError: t is not a constructor
See original GitHub issueBug description

For some reason Tippy causes this error in console. This does not appear every time, perhaps every 1 out of 4 times I visit my site. Not entirely sure what it’s caused by but just looking for a solution.
Reproduction
It is currently being used like this.
$.getScript('https://unpkg.com/popper.js');
$.getScript('https://unpkg.com/tippy.js', function() {
tippy(".allTabsList", {
placement: 'right',
boundary: document.getElementById('page-wrapper'),
touch: false,
theme: 'bbf'
})
});
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
TypeError: "x" is not a constructor - JavaScript - MDN Web Docs
The JavaScript exception "is not a constructor" occurs when there was an attempt to use an object or a variable as a constructor,...
Read more >Javascript "Not a Constructor" Exception while creating objects
The reason is that when it is attempting to initialize y, it creates a temporary "y" object (not class, object!) in the dependency...
Read more >Resolving TypeError: "X" is Not a Constructor in JavaScript
JavaScript "TypeError: "x" is not a constructor" errors occur when invalid objects or a variable is erroneously used as a constructor.
Read more >TypeError: "X" is not a constructor in JavaScript | bobbyhadz
To solve the "TypeError: 'X' is not a constructor" in JavaScript, make sure to only use the new operator on valid constructors, e.g....
Read more >JavaScript TypeError - "X" is not a constructor - GeeksforGeeks
This JavaScript exception is not a constructor that occurs if code tries to use an object or a variable as a constructor, which...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Yeah my bad, new to JS. This seemed to fix it.
Don’t you need to resolve the promise in the $.getScript callback?