Stub node's fs module in webpack #10411
Merged
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
rashidkpc
force-pushed
the
optimizer/fs
branch
from
c162de9 to
880f0e6
Compare
|
Is this being in the 5.3 branch sufficient, or does this need to go into the official 5.3.0 build? |
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.
This stubs out node's
fsmodule when using webpack. The current webpack configuration causes anything that would usually build source maps (eg PostCSS) to fail.Long term, assuming we plan to continue building each app as its own bundle, it would be nice to for plugin authors to be able to specify how they want node builtins handled.