Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pull Request updates dependency webpack from
v3.12.0
tov4.9.1
Release Notes
v4.9.1
Compare Source
Bugfixes
Internal changes
v4.9.0
Compare Source
Features
BannerPlugin
supports a function asbanner
optionserve
property in configuration schemaentryOnly
option toDllPlugin
to only expose modules in the entry pointwebpack-cli
andwebpack-command
usedIds
inrecords
for stablilityBugfixes
splitChunks
when request limit has reached (caused suboptimal splitting)__webpack_require__.e
)runtimeChunk
is even generated when all modules are moved bysplitChunks
(caused multiple runtime chunks instead of single one)Internal changes
many-pages
examplev4.8.3
Compare Source
Bugfixes
debug
dependencyoutput.library.root
v4.8.2
Compare Source
Bugfixes
v4.8.1
Compare Source
Bugfixes
v4.8.0
Compare Source
Features
instantiateStreaming
when availableBugfixes
v4.7.0
Compare Source
Features
import(/* webpackIgnore: true */ "...")
) to keep the import in the bundlechunkGroups
optionnamedChunkGroups
propertyChunk Group
text outputBugfixes
[contenthash:n]
without on-demand-chunksInternal changes
v4.6.0
Compare Source
Features
webpackPrefetch
/webpackPreload
magic comments toimport()
stats.entrypoints[].children
andstats.entrypoints[].childAssets
to stats jsonBugfixes
target: "webworker"
this
toundefined
ESM replacement in function default valuesnew require(...)
is weird, but now behaves like in node.jsexport * from "commonjs"
with partial overrideoutput.globalObject
intarget: "node-webkit"
loadModules
and dependencies in these modulesunknown size
when size is unknownoptimization
configurationInternal changes
v4.5.0
Compare Source
Features
Bugfixes
Contributing
yarn setup
script for bootstrapping local developmentv4.4.1
Compare Source
Bugfixes
v4.4.0
Compare Source
Features
splitChunks.chunks
supports a custom function nowmode
Bugfixes
chunkFilename
, because it's not workingexport default (function xxx() {})
Performance
v4.3.0
Compare Source
Features
[contenthash]
placeholderBugfixes
browser
field is used for targetelectron-renderer
devtoolNamespace
default correctly when passing an object tooutput.library
v4.2.0
Compare Source
Features
splitChunks.automaticNameDelimiter
to configure the name separator for automatic namesstats.excludeModules
now also accept booleansperformance
is disabled by default in non-web targetsBugfixes
events.json
in ProfilingPluginv4.1.1
Compare Source
Features
Bugfixes
sourceMap
option of the default UglifyJsPlugin now defaults to true when the SourceMapDevToolPlugin is usedmodule.assets
is now working again in the StatsdevtoolNamespace
default works now also for arrays passed tooutput.library
chunks
option ofoptimization.splitChunks
v4.1.0
Compare Source
Features
filename
option tooptimization.splitChunks
to modify the filename template for splitted chunksBugfixes
this.xxx
inProvidePlugin
v4.0.1
Compare Source
Features
version
property to webpack exportsBugfixes
import()
with CJS now gives correct exportsv4.0.0
Compare Source
Big changes
mode
or--mode
) between two modes now: production or developmentoptimization.*
(build your custom mode)process.env.NODE_ENV
are set to production or development (only in built code, not in config)none
mode which disables everythingimport()
always returns a namespace object. CommonJS modules are wrapped into the default exportimport()
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)CommonsChunkPlugin
was removed ->optimization.splitChunks
,optimization.runtimeChunk
type: "javascript/auto"
when transforming JSON via loader to JSBig features
javascript/esm
handles ESM more strictly compared tojavascript/auto
:default
import, everything else (including namespace import) emit errors.mjs
modules arejavascript/esm
by defaultimport()
sideEffects: false
is now supported in package.jsonsideEffects
in package.json also supports glob expressions and arrays of glob expressionsoptimization.splitChunks
option was introducedDetails: https://gist.github.com/sokra/1522d586b8e5c0f5072d7565c2bee693
import()
occur in a dead branchwebpackInclude
andwebpackExclude
are supported by the magic comment forimport()
. They allow to filter files when using a dynamic expression.System.import()
now emits a warningRule.parser.system: true
System.import
withRule.parser.system: false
module.rules[].resolve
. It's merged with the global configuration.optimization.minimize
has been added to switch minimizing on/offoptimization.minimizer
has been added to configurate minimizers and optionswebpack-cli
to use the CLI--progress
) now displays plugin namesFeatures
module.rules[].type
options.dependencies
configurations now throw errorsideEffects
can be overriden via module.rulesoutput.hashFunction
can now be a Constructor to a custom hash functionoutput.globalObject
config option to allow to choose the global object reference in runtime exitCodetype
andrequest
.include
test
andexclude
to the eval source map devtool pluginfor of
instead offorEach
Map
andSet
instead of Objectsincludes
instead ofindexOf
text/javascript
andasync
as this are the default values (saves a few bytes)__webpack_require__
and argument is omitted.wasm
,.mjs
,.js
and.json
extensions in this orderoutput.pathinfo
is now on by default in develoment modeentry
defaults to./src
output.path
defaults to./dist
production
defaults when omiting themode
option<{parents}>
>{children}<
and={siblings}=
in StatsbuildAt
time to statsimport()
now emits a error instead of a warningdone
is now an async hookBugfixes
*/
output.chunkCallbackName
to the schema to allow configurating WebWorker templatemodule.id/loaded
now correctly bails out of Module Concatentation (Scope Hoisting)Watching.invalidate
-!
behavior with post loadersrun
andwatchRun
hooks forMultiCompiler
this
is now undefined in ESMvar
,const
orlet
javascript/dynamic
orjavascript/module
is used.buildMeta
of nulloriginal-fs
module for electron targetsplugins
Internal changes
plugin
calls withtap
calls (new plugin system)buildMeta.exportsType: "default"
for json modulesneo-async
instead ofasync
Removed features
module.loaders
loaderContext.options
Compilation.notCacheable
flagNoErrorsPlugin
Dependency.isEqualResource
NewWatchingPlugin
CommonsChunkPlugin
Breaking changes for plugins/loaders
plugin
method is backward-compatibleCompiler.hooks.xxx.tap(<plugin name>, fn)
nowChunk.chunks/parents/blocks
are no longer Arrays. A Set is used internally and there are methods to access it.Parser.scope.renames
andParser.scope.definitions
are no longer Objects/Arrays, but Map/Sets.StackedSetMap
(LevelDB-like datastructure) instead of ArraysCompiler.options
is no longer set while applying pluginsDependency.getReference()
may now return aweak
property.Dependency.weak
is now used by theDependency
base class and returned in the base impl ofgetReference()
Module
sContextModule
andresolveDependencies
Compiler.resolvers
intoCompiler.resolverFactory
accessible with pluginsDependency.isEqualResource
has been replaced withDependency.getResourceIdentifier
Template
are now staticoutputOptions
andrequestShortener
has been moved to this classModule.meta
has been replaced withModule.buildMeta
Module.buildInfo
andModule.factoryMeta
have been addedModule
have been moved into the new objectsloaderContext.rootContext
which points to thecontext
options. Loaders may use it to make stuff relative to the application root.this.hot
flag to loader context when HMR is enabledbuildMeta.harmony
has been replaced withbuildMeta.exportsType: "namespace
map/foreach
Chunks/Modules/Parents
methods are now deprecated/removedcreateGenerator
andgenerator
hooks for NormalModuleFactory to customize code generationThis PR has been generated by Renovate Bot.