Uncaught TypeError: Super expression must either be null or a function, not undefined
See original GitHub issueGetting error this in a production environment, while local dev works without issues.
Using react-dates 18.2.0 18.2.1
Uncaught TypeError: Super expression must either be null or a function, not undefined
at withStyles.js:44
at withStyles.js:44
at withStyles.js:158
at Object.<anonymous> (CalendarDay.js:276)
at o (bootstrap:78)
at Object.<anonymous> (index.js:207)
at o (bootstrap:78)
at Object.<anonymous> (index.js:2)
at o (bootstrap:78)
at Object.<anonymous> (sn.hd.product.js:53)
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (5 by maintainers)
Top Results From Across the Web
Uncaught TypeError: Super expression must either be null or ...
This means that you want subclass something, which should be Class , but is undefined . The ...
Read more >React Errors : Super expression must either be null or a function
Have you come across this error when working with React? Uncaught TypeError: Super expression must either be null or a function, not undefined....
Read more >React Errors : Super expression must either be null or a function
This is all about reactjs giving error Uncaught TypeError: Super expression must either be null or a function, not undefined. Reference :- https ......
Read more >Uncaught TypeError: Super expression must either be null or ...
After making production build i am getting this error in console and application is not getting loaded. My Environment: OS: Linux/Ubuntu ...
Read more >TypeError: Super expression must either be null or a function ...
I got here just by googling the OP's error. In my case, the issue only appears when I run a 'release', minified build,...
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

We’re also experiencing this error in our application code base.
So, I seem to have solved this in our case at least.
In our production webpack task, we are using the uglify-webpackjs-plugin.
Adding the lines:
keep this error from happening in that environment.
Possibly some food for thought on why this issue is happening in the future.