The version 3.1.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.1.0
Updates
Fancy logging; webpack-log is now used for logging to the terminal (webpack-dev-middleware was already using this).
The logLevel option is added for more fine-grained control over the logging.
Bugfixes
MultiCompiler was broken with webpack 4.
Fix deprecation warnings caused by webpack 4. Note that you will still see some deprecation warnings because webpack-dev-middleware has not been updated yet.
Commits
The new version differs by 28 commits ahead by 28, behind by 2.
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.1.0 of webpack-dev-server was just published.
The version 3.1.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.1.0Updates
webpack-logis now used for logging to the terminal (webpack-dev-middleware was already using this).logLeveloption is added for more fine-grained control over the logging.Bugfixes
Commits
The new version differs by 28 commits ahead by 28, behind by 2.
94398c43.1.0d20757bUpgrade another timeout for slow CIf0534fcUse webpack-log for loggingf76182c3.0.1-beta.0c375aa6Fix support for multi compiler in webpack 49921eccAdd basic example for multi-compilerc32cfa8Use non-deprecated webpack 4 API's31d94abMake tests use more webpack 4 goodiness9934724Fix accidental skip of nearly all tests (whoops)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'There are 28 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: