The version 3.0.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 Notesv3.0.0
Changes from 2.6.1 to 3.0.0
Features
node_modules no longer mangle to ~ in stats [breaking change]
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 95.349% when pulling 92230296d471bb266220752c475e99a176c2f0c3 on greenkeeper/webpack-3.0.0 into 3cbcc6393321bfc5a399b7dda066fe0a55a81194 on master.
Version 3.0.0 of webpack just got published.
The version 3.0.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.0.0Changes from 2.6.1 to 3.0.0
Features
node_modules
no longer mangle to~
in stats [breaking change]webpack.optimize.ModuleConcatenationPlugin
)output.libraryExport
to select an export for the librarysourceMapFilename
now supports[contenthash]
[breaking change]module.noParse
supports functionsnode: false
option to disable all node specific additionsBugfixes
async
optionInternal changes
Changes from 3.0.0-rc.2 to 3.0.0
Bugfixes
Internal changes
Commits
The new version differs by 176 commits.
bf4ec9c
3.0.0
9feda63
Merge pull request #5028 from webpack/feature/externalize_uglify_plugin
49d6e38
Merge pull request #5086 from webpack/ci/node-8
3dcb133
OSX test on node.js 8
f4b8785
Merge pull request #5012 from webpack/TheLarkInn-patch-1
d26c402
chore(deps): upgrade uglifyjs-webpack-plugin deps to get latest webpack-sources so tests pass
3da4f3e
Merge pull request #5085 from jbellenger/jbellenger/rawmodule-hash
8c9dc14
fix RawModule hashing
c2c5d73
Update README.md
316d4b9
Merge pull request #5084 from timse/remove-duplicate-code
ae18552
update test case with changed hash due to less clutter in dependencies
fc20348
unite iteration through modules into one loop
083843e
remove code that pushes arrays of dependencies into dependencies
ab636b0
Merge pull request #5075 from andreipfeiffer/master
3b3449c
Refactor: use const for non reassignable identifier
There are 176 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: