-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Uncaught TypeError: Super expression must either be null or a function, not undefined #1456
Comments
In what browser? There’s a known issue in 18.2.0 in IE 9-11, due to a bug in babel around inheritance hierarchies. 18.2.1 fixes it, and 18.2.2 will fix #1455. |
Chrome v70. Also an issue in v69. Happening for other users in Chrome, not sure their versions. Error is happening in Firefox v63 as well. |
And to confirm, you’re not running node_modules through babel? |
It's excluded from babel. |
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. |
Definitely that’s a good change to make; but it shouldn’t be affecting this. It might be a bug in uglify. |
Unfortunately it's not a viable change since we would like to not turn this on across the site. It seems to only be an issue within this library, specifically within |
Can you try 18.2.1? |
Still an issue in 18.2.1 |
We're also experiencing this error in our application code base. |
@danjumamilhaus what version of React are you using? |
Ultimately, upgrading uglifyjs-webpack-plugin to v2.0.1 from v1.2.7 solved this issue. Found the info I needed starting here: facebook/react#13987 (comment) in case some lone traveler is interested. |
Tested using React v16.4.1 |
I had this error, turns out i had misspelled Component, i had written Class blabla extends React.Compnent. |
Getting error this in a production environment, while local dev works without issues.
Using react-dates
18.2.018.2.1The text was updated successfully, but these errors were encountered: