-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of webpack-dev-server is breaking the build 🚨 #65
Comments
Version 2.4.3 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 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.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv2.4.4Bugfixes:
|
Version 2.4.5 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 10 commits0.
false See the full diff |
Version 2.5.0 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 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 21 commits.
There are 21 commits in total. See the full diff |
Version 2.5.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 24 commits.
There are 24 commits in total. See the full diff |
Version 2.4.2 of webpack-dev-server just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As webpack-dev-server is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Release Notes
v2.4.2entry
not working when it was a function (#802).contentBase
as an array did not work when used via CLI (#832).Commits
The new version differs by 15 commits .
60e4727
2.4.2
32adae3
Added beforeunload check to index.js (#544) (#841)
d69559a
Handle external upgrade for all websocket proxies (#843)
35a44d1
Remove Node.js v7 warning
d2f579c
Support for array of contentBase (#832)
aabeeaa
Remove unnecessary logging of closing the dev-server
1dc9461
Fix to share proxy option between proxy settings when the proxy option is a same object (#836)
42cd23c
Explicitely but gracefully handle SIGINT and SIGTERM signals. (#787)
85de417
Use arrow function if it possible and get rid of .bind in server part (#835)
234294a
Add unit tests for proxy options (#834)
8d4b826
add codecov
d081f01
Update
webpack-dev-middleware
to 0.17.4 (#827)ccc8163
Fix exception when client script is used in webworkers (#813)
f996bd4
fix typo and add
--open
(#814)690df60
devClient does not work with dynamic entry. (#802)
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 🌴
The text was updated successfully, but these errors were encountered: