-
Notifications
You must be signed in to change notification settings - Fork 200
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
Crash after migrating webpack 4 -> 5 with new JSX transforms #176
Comments
related to #85. |
@delyanr, can you please try importing
I reproduced the issue and solved it with this change here: |
@vzaidman, yes this stops the crash. As per my original post, also Finally, I don't believe changing the imports is the right solution here anyway, since the React team is likely to change the behavior of the default imports in the future as stated in their blog post here. Thanks for looking into this. |
Did you change the react-preset in the babel config to:
? And yes, I'm aware of the React's team decision regarding default imports. I hope I'll be able to come up with a solution to this problem by then... |
Ahh, indeed, I botched the babel config. I can confirm that
Unfortunately, it still crashes with |
Great! |
Hello. I'm in the process of migrating from
webpack@4
towebpack@5
. After doing so, I started getting an uncaught TypeError fromwhy-did-you-render
.I believe this is also connected with the latest React JSX transform (I'm using
react@16.14
). At the top of the file I have:If I revert back to
webpack@4
and keep the latest JSX transform - it works.If I keep
webpack@5
and revert back to the old React imports - it works.If I use both together - I get the crash above.
Thanks!
The text was updated successfully, but these errors were encountered: