The version 3.0.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-dev-server.
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 Notesv3.0.0
Updates
Breaking change: webpack v4 is now supported. Older versions of webpack are not supported.
Breaking change: drops support for Node.js v4, going forward we only support v6+ (same as webpack).
webpack-dev-middleware updated to v2 (see changes).
Bugfixes
After starting webpack-dev-server with an error in your code, it would not reload the page after fixing that error (#1317).
DynamicEntryPlugin is now supported correctly (#1319).
Huge thanks to all the contributors!
Please note that webpack-serve will eventually be the successor of webpack-dev-server. The core features already work so if you're brave enough give it a try!
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 3.0.0 of webpack-dev-server was just published.
The version 3.0.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-dev-server.
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.0.0Updates
Bugfixes
Huge thanks to all the contributors!
Please note that webpack-serve will eventually be the successor of webpack-dev-server. The core features already work so if you're brave enough give it a try!
Commits
The new version differs by 20 commits.
6e1d8863.0.0eedf10fTry again at fixing CI by upping timeout (necessary for node v6)dfe137cHopefully fix failing CI tests (the hacky way)1e7accaActually make the yargs version test do somethingcdd10faStop testing node v4 on travis ci7378e3eMerge branch 'webpack-4'ab4eeb0Fix page not reloading after fixing first error on page (#1317)dbea323Update depsf4f14ceFix support for DynamicEntryPlugin (#1319)398c7733.0.0-beta.2cdc7288Simplify build webpack configs thanks to webpack 4e603e0dAllow no publicPath or entry point (#1310)9852a5f3.0.0-beta.16db2e85Fix tests after webpack v4 upgradeeb2f0a9Fix option rename in webpack-dev-middlewareThere are 20 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: