Releases: webpack/webpack-dev-middleware
Releases · webpack/webpack-dev-middleware
v1.10.2
Security 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.
middleware(compiler, {
headers: {
"Access-Control-Allow-Origin": "your-host"
}
})Read more about CORS here: https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
Bugfixes:
- Remove
Access-Control-Allow-Origin=*default
v1.10.1
v1.10.0
v1.9.0
v1.8.4
v1.8.3
The last few releases had a few bugs in them that shouldn't have reached stable. We're working hard on adding enough tests to prevent these kind of failures.
v1.8.2
v1.8.1
v1.8.0
- Add tests for everything (#121)!
- Use valid license for npm (af6243b).
- Instantiate the in-memory filesystem only once, meaning it can be shared when using multiple middleware instances with one webpack config (#120).
- When sending requests with a
Rangeheader, the status code would not always be correct (cedc09f). - Middleware would not work with a proxy (#80).
- Add
indexoption (default:index.html) to customize the file used as index for a directory (#123).
v1.7.0
- Add
reporteroption for custom logs (#91). - Add
serverSideRenderoption to help support server-side rendering (#118). - Set
statusCodeto 200 for served files (#94). - Fix
waitUntilValidcallback always being called immediately when using MultiCompiler (#100). - Fix range support not working (#116).
- Only use middleware for GET requests (#96).