Update webpack-dev-server to the latest version 🚀#29
Conversation
Version 2.4.1 just got published.Update to this version instead 🚀 Release Notesv2.4.1
|
Version 2.4.2 just got published.Update to this version instead 🚀 Release Notesv2.4.2
CommitsThe new version differs by 15 commits .
See the full diff. |
Version 2.4.3 just got published.Update to this version instead 🚀 Release Notesv2.4.3Security fix:This version contains a security fix, which is also breaking change if you have an insecure configuration. We added a check for the correct The The response will contain a note when using an incorrect For usage behind a Proxy or similar setups we also added a This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2 Note: This only affect the development server and middleware. webpack and built bundles are not affected. Bugfixes:
Features:
|
Version 2.4.4 just got published.Update to this version instead 🚀 Release Notesv2.4.4Bugfixes:
|
Version 2.4.5 just got published. |
Version 2.5.0 just got published.Update to this version instead 🚀 Release Notesv2.5.0SecurityDon't provide a SSL cert, but generate one on demand. Unique for each developer. https://medium.com/@mikenorth/961572624c54 by Mike North Bugfixes
CommitsThe new version differs by 11 commits.
See the full diff |
Version 2.5.1 just got published. |
Version 2.6.0 just got published.Update to this version instead 🚀 Release Notesv2.6.0CommitsThe new version differs by 10 commits ahead by 10, behind by 1.
See the full diff |
Version 2.6.1 just got published.Update to this version instead 🚀 Release Notesv2.6.1
|
Version 2.7.0 just got published.Update to this version instead 🚀 Release Notesv2.7.0FeaturesBugfixesCommitsThe new version differs by 6 commits.
See the full diff |
Version 2.7.1 just got published. |
Version 2.4.0 of webpack-dev-server just got published.
The version 2.4.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-dev-server.
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.
Commits
The new version differs by 238 commits (ahead by 238, behind by 39).
3f7c9f72.4.0e22317fSetting contentBase to false with historyApiFallback on works properly #791 (#797)b85a0ceExtract logic of adding entry points (#782)4991704feat - Allow overlay to be enabled for warnings (#789) (#790)9d2925cUpdate dependencies0099613Handle promise rejection when using--openflag (#780)04eafa52.3.0ac1675cRefactor config validationd725fd9Implement error overlay (#764)61e5403Allow a string to be passed as theportconfig option (#766)2cf2939have --open use the options.public path if it exists (#749)aa989972.2.1686dec4Fix inline example not working after webpack 2.2.0c82c1ebOnly run Travis on themasterbranch [skip ci]54b4b02update examples to reflect web pack 2.2.0 (#759)There are 238 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 🌴