Update webpack to the latest version 🚀 #1447
Closed
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.
Version 3.5.0 of webpack just got published.
The version 3.5.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of webpack.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v3.5.0Features:
stats.excludeAssetsto allow to filter assets in list (@ldrick)import(/* webpackMode: "weak" */ "module")to try to load a module without network request (@faceyspacey)require.contextwhich is the context mode. Can befalse,"eager","lazy-once","weak"and"async-weak". (@faceyspacey)require.resolveWeaknow support expressions (@faceyspacey)ModuleConcatenationPlugin)Bugfixes:
ModuleConcatenationPluginConcatenatedModule--helpoutput is flushed before process exit (@esbenp)statsoptions are now validated by schema (@esbenp)CommonsChunkPluginin async mode withoutnameargument--resolve-extensions(@tomek-d)has no internal namewhen using dependency variable in root of scope-hoisted modules (ModuleConcatenationPlugin)Examples:
Commits
The new version differs by 68 commits.
75a8ffe3.5.0afa28c0Merge pull request #5453 from webpack/bugfix/import-order-scope-hoistinga569764Merge pull request #5457 from tomek-d/resolve-extensions-typo0b8023afixes #509629d1336Fixed bug in --resolve-extensions parameter documentation39051dfupdate example7619c43generate more pretty names for nested concatenation6607cfaremove ordering in ModuleConcatenationPlugin2bbbf50Merge pull request #5437 from esbenp/fix-help-output-test-53459f5bffabeautify334c1c4remove unused variable8835751fix conflict handling7099fccupdate stats test caseb77a52badd reserved words to avoid syntax errors16a5831use old new Buffer api for node 4There are 68 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴