webpack
5.112.2 · 23 Oct 2026MIT76.9M / weekRepositorynpmAtom feed
Upgrading webpack From 3.12.0 to 4.0.0
1 release in betweenevery note read
- 35
- changes to make
- 0
- advisories fixed
- 23
- new
- 12
- fixes
Before you upgrade
Tick each one off as you go- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
- Breaking4.0.0
Release by release
- Breaking
CommonsChunkPluginwas removed ->optimization.splitChunks,optimization.runtimeChunk - Breaking
Removed
module.loaders - Breaking
Removed
loaderContext.options - Breaking
Removed
Compilation.notCacheableflag
- Breaking
60 other lines we could not sort, mostly version bumps
- 4.0.0
Node.js 4 is no longer supported. Source Code was upgraded to a higher ecmascript version.
- 4.0.0
You have to choose (
modeor--mode) between two modes now: production or development - 4.0.0
import()always returns a namespace object. CommonJS modules are wrapped into the default export - 4.0.0
NoEmitOnErrorsPlugin->optimization.noEmitOnErrors(on by default in production mode) - 4.0.0
ModuleConcatenationPlugin->optimization.concatenateModules(on by default in production mode) - 4.0.0
NamedModulesPlugin->optimization.namedModules(on by default in develoment mode) - 4.0.0
Webpack now handles JSON natively
- 4.0.0
javascript/auto: (The default one in webpack 3) Javascript module with all module systems enabled: CommonJS, AMD, ESM
- 4.0.0
javascript/esm: EcmaScript modules, all other module system are not available
- 4.0.0
javascript/dynamic: Only CommonJS and, EcmaScript modules are not available
11 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.