Super expression must either be null or a function while loading wavesurfer
See original GitHub issueAfter upgrading to latest version 3.1.0 of wavesurfer. below error is coming while loading wavesurfer.js file.
ERROR Error: Uncaught (in promise): TypeError: Super expression must either be null or a function (core.js.pre-build-optimizer.js:1449)
TypeError: Super expression must either be null or a function
It was working correctly for older version 3.0.0
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:14
Top Results From Across the Web
Using Angular and nginx I get the error Uncaught TypeError
Using Angular and nginx I get the error Uncaught TypeError: Super expression must either be null or a function.
Read more >React Errors : Super expression must either be null or a ...
This is an easy to find and fix issue. If a component is exported with the default keyword then it must be imported...
Read more >Uncaught TypeError: Super expression must either be null ...
After making production build i am getting this error in console and application is not getting loaded. My Environment: OS: Linux/Ubuntu ...
Read more >wavesurfer.js resize doesn't stops playback
__esModule)return e;var t={};if(null!=e)for(var n in e)Object.prototype. ... new TypeError("Super expression must either be null or a function, not "+typeof ...
Read more >React Errors : Super expression must either be null or a ...
Upgrade React. React has only supported ES6-style classes since version 0.13.0 (see their official blog post on the support introduction here.
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 FreeTop 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
Top GitHub Comments
maybe we must change
main
definition in package.json and do not use the minified version i have no time currently to test itsounds good @aburai. see https://docs.npmjs.com/files/package.json#main