Use the latest npm version of webpack, now that v4 is officially released #9
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
Now with the v4 release of weblack, instead of using it from github, switched to use the latest npm version
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.
Now with the v4 release of webpack, instead of getting the latest version from GitHub, I've switched to use the latest version on npm, because that's what the user would normally get.
I'm not sure if there are optimizations on npm's version or not, but to me, it seems more of a "real world" comparison if we actually use the same version that the user would normally install on the project 😃
What do you think?
I've bumped the other packages too, including
parcel-bundler