Update webpack-dev-middleware to the latest version 🚀 #1778
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 1.10.2 of webpack-dev-middleware just got published.
The version 1.10.2 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-middleware.
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
v1.10.2Security fix:
This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.
We removed setting
Access-Control-Allow-Origin
to*
be default. This allowed evil websites to access your assets.Instead we ask you to set
Access-Control-Allow-Origin
manually to your host if required in your setup.Use the
headers
option to do so.Read more about CORS here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
Bugfixes:
Access-Control-Allow-Origin
=*
defaultCommits
The new version differs by 10 commits0.
9b03d79
1.10.2
c59b3b3
Merge remote-tracking branch 'remotes/origin/add-node-7-travis'
626a35a
remove security risk
798b2f1
Avoid setting http status code explicitly (#175)
1e01626
adding node 7 to travis config (#185)
d986c2e
Merge pull request #176 from piperchester/patch-1
9b9ffee
fixing some number typos in the tests
d3dfe67
adding node 7 to travis config
0ce28c7
Fix link to Kees
bd6a593
use decodeURIComponent for getFilenameFromUrl final output (#173)
false
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 🌴