webpack
5.112.2 · 23 Oct 2026MIT76.9M / weekRepositorynpmAtom feed
Upgrading webpack From 5.68.0 to 5.69.0
1 release in betweenevery note read
Security
4 advisories still affect 5.69.0
- webpack buildHttp HttpUriPlugin allowedUris bypass via HTTP redirects → SSRF + cache persistencelow · GHSA-38r7-794h-5758
- Webpack's AutoPublicPathRuntimeModule has a DOM Clobbering Gadget that leads to XSSmoderate · GHSA-4vvj-4cpr-p986
- webpack buildHttp: allowedUris allow-list bypass via URL userinfo (@) leading to build-time SSRF behaviorlow · GHSA-8fgc-7cc6-rx7x
- Cross-realm object access in Webpack 5critical · GHSA-hc6q-2mpp-qw7j
Upgrading to 5.104.1 clears them.
Release by release
- New
Automatically switch to an ESM compatible environment when enabling ESM output mode
- New
Handle multiple alternative directories (e. g. due to
resolve.aliasorresolve.modules) when creating an context module - New
Add
util/typesto node.js built-in modules - New
Add
__webpack_exports_info__.<name>.canMangleapi
- New
1 other line we could not sort, mostly version bumps
- 5.69.0
Update typescript and jest
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.