-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: Super expression must either be null or a function, not undefined #151
Comments
Hard to say what might be happening here without more information. According to this Stack Overflow post, it looks like this might happen if something extends Could you post some of the code from your stack trace? |
Thanks for looking into this. I will try and create a standalone app to demonstrate this error. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I found the same problem, removing UglifyJS from webpack config fixed it but I thought this is not the best solution.
But I still don't understand how does this option affects the build |
For anyone who run into this issue setting |
Try to add
|
This is due to an underlying correctness issue in Terser/Uglify, as per my issue reference. |
@marcusdarmstrong thanks! Closing this in favor of that terser/terser#308. |
I am getting this error after upgrading to webpack v4. Strangely this happens only in the prod build and not in dev build.
This is the stack-trace in browser console:
I am actually using
react-dates
which is using this library. From stacktrace, I suspect this is where the error is coming from. Also removingreact-dates
makes the error to go away.Here is my entire webpack config: https://gist.github.com/tejasbubane/9ae4d2e099bef97b3b118f99a163294e
Relevant libraries and their versions:
The text was updated successfully, but these errors were encountered: