webpack
5.112.2 · 23 Oct 2026MIT76.9M / weekRepositorynpmAtom feed
4.47.0 is the newest release of 4.x.
In short
27 breaking8 removed11 new12 faster12 fixed60 changed11 internal
- Breaking
New major version of enhanced-resolve
- Breaking
Templates for chunks may now generate multiple assets
- Breaking
Chunk.chunks/parents/blocksare no longer Arrays. A Set is used internally and there are methods to access it. - Breaking
Parser.scope.renamesandParser.scope.definitionsare no longer Objects/Arrays, but Map/Sets. - Breaking
Parser uses
StackedSetMap(LevelDB-like datastructure) instead of Arrays - Breaking
Compiler.optionsis no longer set while applying plugins - Breaking
Harmony Dependencies has changed because of refactoring
- Breaking
Dependency.getReference()may now return aweakproperty.Dependency.weakis now used by theDependencybase class and returned in the base impl ofgetReference()
Release note
Big changes
Environment
Node.js 4 is no longer supported. Source Code was upgraded to a higher ecmascript version.
Usage
You have to choose (
modeor--mode) between two modes now: production or developmentproduction enables all kind of optimizations to generate optimized bundles
development enables comments and hint for development and enables the eval devtool
production doesn't support watching, development is optimized for fast incremental rebuilds
production also enables module concatenating (Scope Hoisting)
You can configure this in detail with the flags in
optimization.*(build your custom mode)process.env.NODE_ENVare set to production or development (only in built code, not in config)There is a hidden
nonemode which disables everything
Syntax
import()always returns a namespace object. CommonJS modules are wrapped into the default exportThis probably breaks your code, if you used to import CommonJs with
import()
Configuration
You no longer need to use these plugins:
NoEmitOnErrorsPlugin->optimization.noEmitOnErrors(on by default in production mode)ModuleConcatenationPlugin->optimization.concatenateModules(on by default in production mode)NamedModulesPlugin->optimization.namedModules(on by default in develoment mode)
CommonsChunkPluginwas removed ->optimization.splitChunks,optimization.runtimeChunk
JSON
webpack now handles JSON natively
You may need to add
type: "javascript/auto"when transforming JSON via loader to JSJust using JSON without loader should still work
allows to import JSON via ESM syntax
unused exports elimination for JSON modules
Optimization
Upgrade uglifyjs-webpack-plugin to v1
ES15 support
Big features
Modules
webpack now supports these module types:
javascript/auto: (The default one in webpack 3) Javascript module with all module systems enabled: CommonJS, AMD, ESM
javascript/esm: EcmaScript modules, all other module system are not available
javascript/dynamic: Only CommonJS and, EcmaScript modules are not available
json: JSON data, it's available via require and import
webassembly/experimental: WebAssembly modules (currently experimental)
javascript/esmhandles ESM more strictly compared tojavascript/auto:Imported names need to exist on imported module
Dynamic modules (non-esm, i. e. CommonJs) can only imported via
defaultimport, everything else (including namespace import) emit errors
In
.mjsmodules arejavascript/esmby defaultWebAssembly modules
can import other modules (JS and WASM)
Exports from WebAssembly modules are validated by ESM import
You'll get a warning/error when trying to import a non-existing export from WASM
can only be used in async chunks. They doesn't work in initial chunks (would be bad for web performance)
Import modules using WASM via
import()
This is an experimental feature and subject of change
Optimization
sideEffects: falseis now supported in package.jsonsideEffectsin package.json also supports glob expressions and arrays of glob expressions
Instead of a JSONP function a JSONP array is used -> async script tag support, order no longer matter
New
optimization.splitChunksoption was introduced
Details: gist.github.com/sokra/1522d586b8e5c0f5072d7565c…Dead branches are now removed by webpack itself
Before: Uglify removed the dead code
Now: webpack removes the dead code (in some cases)
This prevents crashing when
import()occur in a dead branch
Syntax
webpackIncludeandwebpackExcludeare supported by the magic comment forimport(). They allow to filter files when using a dynamic expression.Using
System.import()now emits a warningYou can disable the warning with
Rule.parser.system: trueYou can disable
System.importwithRule.parser.system: false
Configuration
Resolving can now be configured with
module.rules.resolve. It's merged with the global configuration.optimization.minimizehas been added to switch minimizing on/offBy default: on in production mode, off in development mode
optimization.minimizerhas been added to configurate minimizers and options
Usage
Some Plugin options are now validated
CLI has been move to webpack-cli, you need to install
webpack-clito use the CLIThe ProgressPlugin (
--progress) now displays plugin namesAt least for plugins migrated to the new plugin system
Performance
UglifyJs now caches and parallizes by default
Multiple performance improvements, especially for faster incremental rebuilds
performance improvement for RemoveParentModulesPlugin
Stats
Stats can display modules nested in concatenated modules
Features
Configuration
Module type is automatically choosen for mjs, json and wasm extensions. Other extensions need to be configured via
module.rules.typeIncorrect
options.dependenciesconfigurations now throw errorsideEffectscan be overriden via module.rulesoutput.hashFunctioncan now be a Constructor to a custom hash functionYou can provide a non-cryto hash function for performance reasons
add
output.globalObjectconfig option to allow to choose the global object reference in runtime exitCode
Runtime
Error for chunk loading now includes more information and two new properties
typeandrequest.
Devtool
remove comment footer from SourceMaps and eval
add support for
includetestandexcludeto the eval source map devtool plugin
Performance
webpacks AST can be passed directly from loader to webpack to avoid extra parsing
Unused modules are no longer unnecessarly concatenated
Add a ProfilingPlugin which write a (Chrome) profile file which includes timings of plugins
Migrate to using
for ofinstead offorEachMigrate to using
MapandSetinstead of ObjectsMigrate to using
includesinstead ofindexOfReplaced some RegExp with string methods
Queue don't enqueues the same job twice
Use faster md4 hash for hashing by default
Optimization
When using more than 25 exports mangled export names are shorter.
script tags are no longer
text/javascriptandasyncas this are the default values (saves a few bytes)The concatenated module now generates a bit less code
constant replacements now don't need
__webpack_require__and argument is omitted
Defaults
webpack now looks for the
.wasm,.mjs,.jsand.jsonextensions in this orderoutput.pathinfois now on by default in develoment modein-memory caching is now off by default in production
entrydefaults to./srcoutput.pathdefaults to./distUse
productiondefaults when omiting themodeoption
Usage
Add detailed progress reporting to SourceMapDevToolPlugin
removed plugins now give a useful error message
Stats
Sizes are now shown in kiB instead of kB in Stats
entrypoints are now shows by default in Stats
chunks now display
<{parents}>>{children}<and={siblings}=in Statsadd
buildAttime to statsstats json now includes the output path
Syntax
A resource query is supported in context
Referencing entry point name in
import()now emits a error instead of a warningUpgraded to acorn 5 and support ES 2018
Plugins
doneis now an async hook
Bugfixes
Generated comments no longer break on
*/Webpack no longer modifies the passed options object
Compiler "watch-run" hook now has the Compiler as first parameter
Add
output.chunkCallbackNameto the schema to allow configurating WebWorker templateUsing
module.id/loadednow correctly bails out of Module Concatentation (Scope Hoisting)OccurenceOrderPlugin now sorts modules in correct order (instead of reversed)
Timestamps for files are read from watcher when calling
Watching.invalidateFix incorrect
-!behavior with post loadersAdd
runandwatchRunhooks forMultiCompilerthisis now undefined in ESMVariableDeclaration are correctly identified as
var,constorletParser now parse the source code with the correct source type (module/script) when the module type
javascript/dynamicorjavascript/moduleis used.Don't crash on missing modules with
buildMetaof nullAdd
original-fsmodule for electron targetsHMRPlugin can be added to the Compiler outside of
plugins
Removed features
- Removed
Removed
module.loaders - Removed
Removed
loaderContext.options - Removed
Removed
Compilation.notCacheableflag - Removed
Removed
NoErrorsPlugin - Removed
Removed
Dependency.isEqualResource - Removed
Removed
NewWatchingPlugin - Removed
Removed
CommonsChunkPlugin
Breaking changes for plugins/loaders
- Breaking
New plugin system
pluginmethod is backward-compatiblePlugins should use
Compiler.hooks.xxx.tap(<plugin name>, fn)now
- Breaking
New major version of enhanced-resolve
- Breaking
Templates for chunks may now generate multiple assets
- Breaking
Chunk.chunks/parents/blocksare no longer Arrays. A Set is used internally and there are methods to access it. - Breaking
Parser.scope.renamesandParser.scope.definitionsare no longer Objects/Arrays, but Map/Sets. - Breaking
Parser uses
StackedSetMap(LevelDB-like datastructure) instead of Arrays - Breaking
Compiler.optionsis no longer set while applying plugins - Breaking
Harmony Dependencies has changed because of refactoring
- Breaking
Dependency.getReference()may now return aweakproperty.Dependency.weakis now used by theDependencybase class and returned in the base impl ofgetReference() - Breaking
Constructor arguments changed for all
Modules - Breaking
Merged options into options object for
ContextModuleandresolveDependencies - Breaking
Changed and renamed dependencies for `import()
- Breaking
Moved
Compiler.resolversintoCompiler.resolverFactoryaccessible with plugins - Breaking
Dependency.isEqualResourcehas been replaced withDependency.getResourceIdentifier - Breaking
Methods on
Templateare now static - Breaking
A new RuntimeTemplate class has been added and
outputOptionsandrequestShortenerhas been moved to this classMany methods has been updated to use the RuntimeTemplate instead
We plan to move code which accesses the runtime to this new class
- Breaking
Module.metahas been replaced withModule.buildMeta - Breaking
Module.buildInfoandModule.factoryMetahave been added - Breaking
Some properties of
Modulehave been moved into the new objects - Breaking
Added
loaderContext.rootContextwhich points to thecontextoptions. Loaders may use it to make stuff relative to the application root. - Breaking
Add
this.hotflag to loader context when HMR is enabled - Breaking
buildMeta.harmonyhas been replaced withbuildMeta.exportsType: "namespace - Breaking
The chunk graph has changed:
Before: Chunks were connected with parent-child-relationships.
Now: ChunkGroups are connected with parent-child-relationships. ChunkGroups contain Chunks in order.
Before: AsyncDependenciesBlocks reference a list of Chunks in order.
Now: AsyncDependenciesBlocks reference a single ChunkGroup.
- Breaking
file/contextTimestamps are Maps now
- Breaking
map/foreachChunks/Modules/Parentsmethods are now deprecated/removed - Breaking
NormalModule accept options object in Constructor
- Breaking
Added required generator argument for NormalModule
- Breaking
Added
createGeneratorandgeneratorhooks for NormalModuleFactory to customize code generation - Breaking
Allow to customize render manifest for Chunks via hooks
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.