Update webpack to the latest version 🚀 #17
Merged
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.10.0 of webpack was just published.
The version 3.10.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of webpack.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v3.10.0Features:
publicPathandfileContextto SourceMapDevToolPluginrequire.includeno longer uses all exports (Tree Shaking)Commits
The new version differs by 11 commits.
c71fd053.10.02c244d2Merge pull request #6061 from webpack/bugfix/require-include-exports00cd8b4allow tree-shaking for require.include905a8f1Merge pull request #5986 from EugeneHlushko/feature-sourcemap-use-filename-in-url5acbe2f3.9.17cca6bbMerge pull request #6044 from webpack/bugfix/schema-watch-optionsa71284eAdd missing watchOptions properties to schema471e1a2make url only relative when no publicPath has been provideda539f24SourceMapDevToolPlugin: update test config with example from change request612111aSourceMapDevToolPlugin: Second test case, make sure sourcemap file is written to expected directory considering the fileContext was provided840b43fSourceMapDevToolPlugin: add fileContext and publicPath options. Add a configCase testSee the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴