-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
upgrades including webpack 5 #13392
upgrades including webpack 5 #13392
Conversation
Is this also now stale? |
Would it be possible to publish a special alpha release on npm from this branch? Since it's not possible to install github sub-directories with npm, that means folks would have to tarball a cloned version. We've moved completely to Webpack 5 and I imagine a lot of folks who have moved to Webpack 5 do not need Webpack 4 backwards compat. So while you guys sort that out we can use |
@timkindberg hoping to have a version to release in a proper alpha next week #13808 |
closing in favor of #13808 |
Issue: #9216
What I did
I think this PR replaces:
#12999
#12964
#11326
This PR should be broken into multiple smaller PRs, really this was a spike to try how close we are to webpack 5 support.
We should collaborate with CRA (@mrmckeb ) on when webpack 5 support is planned.
This PR has NO backwards compatibility for webpack 4. So we either have to come up with a strategy to add backwards compatibility somehow, OR this is a major breaking change, and a pretty disruptive one at that.