webpack
5.112.2 · 23 Oct 2026MIT76.9M / weekRepositorynpmAtom feed
Upgrading webpack From 5.111.1 to 5.112.2
3 releases in betweenevery note read
- 4
- changes to make
- 0
- advisories fixed
- 29
- new
- 133
- fixes
Before you upgrade
Tick each one off as you go- Breaking5.112.1
- Breaking5.112.0
- Deprecated5.112.0
- Deprecated5.112.0
Release by release
- Fixed
Reduce repeated scans when concatenating imported modules.
- Fixed
Avoid allocating CSS module sets for single-group chunks.
- Fixed
Return the value of every module type loaded with
importModule().
- Fixed
- Breaking
Drop more unused functions, arguments, calls, global reads and variable copies when minifying JavaScript.
- New
Support
concatenateModuleswithcacheUnaffected. - New
Speed up startup and CSS minification, sharing the compile cache with workers.
- Fixed
Rebuild a lazy barrel in watch when what it defers changes, and keep the imports and re-exports it still runs.
- Breaking
- Breaking
Require
minimizer-webpack-plugin5.12, so inline scripts in HTML minify again. - Deprecated
Export more plugins under their scope, move eleven loose exports under theirs, deprecate the old, and expose
template.DependencyTemplate,module.NullFactoryandutil.makeSerializable. - Deprecated
Rename the
Harmony*names toESM*and deprecate the old spellings. - New
Apply
pluginsset on a multi-configuration array to theMultiCompiler.
- Breaking
5 internal lines (docs, tests, tooling) left out.
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.