Move node polyfills in webpack to prepare for webpack 5 #7914
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andriijas
requested review from
ianschmitz,
iansu,
mrmckeb and
petetnt
as code owners
ianschmitz
approved these changes
Nov 3, 2019
Closed
|
Closing in favor of #10198 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've started to work on webpack 5 in CRA and I will make a draft PR soon.
Webpack 5 removes automatic node.js polyfills (Concerns: Link mentions automatic pollyfill removal might not make it to final release depending on community feedback)
In preparation for that I replaced the webpack polyfill with a 3rd party.
https://github.com/browserify/path-browserify/