webpack
5.112.2 · 23 Oct 2026MIT76.9M / weekRepositorynpmAtom feed
5.113.0 is the newest release of 5.x.
In short
1 deprecated10 new11 fixed1 internal
- Deprecated
All deprecated methods and options now have
@deprecatedflag in types.
Release note
Minor Changes
Add
exportType: "style"for CSS modules to inject styles into DOM via HTMLStyleElement, similar to style-loader functionality.Add
contextoption support for VirtualUrlPluginThe context for the virtual module. A string path. Defaults to 'auto', which will try to resolve the context from the module id.
Support custom context path for resolving relative imports in virtual modules
Add examples demonstrating context usage and filename customization
Generate different
CssModuleinstances for differentexportTypevalues.Added the
localIdentHashFunctionoption to configure the hash function to be used for hashing.
Additionally, thelocalIdentNameoption can now be a function.Added support for destructuring assignment
requirein cjs, allowing for tree shaking.Added the
validateoption to enable/disable validation in webpack/plugins/loaders, also implemented API to make it inside plugins.Added
sourcesupport for async WASM modules.
Patch Changes
Add a static getSourceBasicTypes method to the Module class to prevent errors across multiple versions.
Included fragment groups in the conflicting order warning for CSS.
Avoid rendering unused top-level
__webpack_exports__declaration when output ECMA module library.Fixed resolving in CSS modules.
Allow external modules place in async chunks when output ECMA module.
Implement
deprecateflag in schema for better TypeScript support to show which options are already deprecated by the configurationSet
.nameto"default"for anonymous default export functions and classes per ES specHash entry chunks after runtime chunks to prevent stale content hash references in watch mode
Correct url() path resolution and preserve source maps for non-link CSS export types (style, text, css-style-sheet)
Emit error when proxy server returns non-200 status code in HttpUriPlugin instead of silently failing.
import.metaas standalone expression now returns a complete object with known properties (url,webpack,main,env) instead of an empty object({}), and hoists it as a module-level variable to ensureimport.meta === import.metaidentity. Inpreserve-unknownmode (ESM output), the hoisted object merges runtimeimport.metaproperties viaObject.assign.Fix incorrect condition in FileSystemInfo that always evaluated to false, preventing trailing slash removal from directory paths during build dependency resolution.
VirtualUrlPlugin absolute path virtual module IDs getting concatenated with compiler context
When a virtual module ID is an absolute path (e.g.
virtual:C:/project/user.js), the auto-derived context was incorrectly joined withcompiler.context, producing a concatenated path likeC:\cwd\C:\project. Now absolute-path contexts are used directly.- Deprecated
All deprecated methods and options now have
@deprecatedflag in types. Fix
CompatibilityPluginto correctly rename__webpack_require__when it appears as an arrow function parameter (e.g.(__webpack_module, __webpack_exports, __webpack_require__) => { ... }).
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.