webpack

Subcommands

NameDescription
build,bundle,bRun webpack (default command, can be omitted)
configtest,tValidate a webpack configuration
help,hDisplay help for command and options
info,iDisplay information about your system
init,create,c,new,nInitialize a new webpack project
loader,lScaffold a webpack loader
plugin,pScaffold a webpack plugin
serve,server,sRun the webpack development server
version,vDisplay the version number of webpack, webpack-cli, and webpack-dev-server commands
watch,wRun webpack and watch for file changes

Options

NameDescription
--config,-c <command...>Provide path to a webpack configuration file e.g. ./webpack.config.js
--config-name <command...>Name of the configuration to use
--merge,-mMerge two or more configurations using 'webpack-merge'
--env <command...>Environment passed to the configuration when it is a function
--node-env <command>Sets process.env.NODE_ENV to the specified value
--hot,-h [command]Enables Hot Module Replacement
--no-hotDisables Hot Module Replacement
--analyzeIt invokes webpack-bundle-analyzer plugin to get bundle information
--progress [command]Print compilation progress during build
--prefetch <command>Prefetch this request
--json,-j [command]Prints result as JSON or store it in a file
--no-amdNegative 'amd' option
--bailReport the first error as a hard error instead of tolerating it
--no-bailNegative 'bail' option
--cacheEnable in memory caching. Disable caching
--no-cacheNegative 'cache' option
--cache-cache-unaffectedAdditionally cache computation of modules that are unchanged and reference only unchanged modules
--no-cache-cache-unaffectedNegative 'cache-cache-unaffected' option
--cache-max-generations <command>Number of generations unused cache entries stay in memory cache at minimum (1 = may be removed after unused for a single compilation, ..., Infinity: kept forever)
--cache-type <command>In memory caching. Filesystem caching
--cache-allow-collecting-memoryAllows to collect unused memory allocated during deserialization. This requires copying data into smaller buffers and has a performance cost
--no-cache-allow-collecting-memoryNegative 'cache-allow-collecting-memory' option
--cache-cache-directory <command>Base directory for the cache (defaults to node_modules/.cache/webpack)
--cache-cache-location <command>Locations for the cache (defaults to cacheDirectory / name)
--cache-compression <command>Compression type used for the cache files
--no-cache-compressionNegative 'cache-compression' option
--cache-hash-algorithm <command>Algorithm used for generation the hash (see node.js crypto package)
--cache-idle-timeout <command>Time in ms after which idle period the cache storing should happen
--cache-idle-timeout-after-large-changes <command>Time in ms after which idle period the cache storing should happen when larger changes has been detected (cumulative build time > 2 x avg cache store time)
--cache-idle-timeout-for-initial-store <command>Time in ms after which idle period the initial cache storing should happen
--cache-immutable-paths <command...>A RegExp matching an immutable directory (usually a package manager cache directory, including the tailing slash) A path to an immutable directory (usually a package manager cache directory)
--cache-immutable-paths-resetClear all items provided in 'cache.immutablePaths' configuration. List of paths that are managed by a package manager and contain a version or hash in its path so all files are immutable
--cache-managed-paths <command...>A RegExp matching a managed directory (usually a node_modules directory, including the tailing slash) A path to a managed directory (usually a node_modules directory)
--cache-managed-paths-resetClear all items provided in 'cache.managedPaths' configuration. List of paths that are managed by a package manager and can be trusted to not be modified otherwise
--cache-max-age <command>Time for which unused cache entries stay in the filesystem cache at minimum (in milliseconds)
--cache-max-memory-generations <command>Number of generations unused cache entries stay in memory cache at minimum (0 = no memory cache used, 1 = may be removed after unused for a single compilation, ..., Infinity: kept forever). Cache entries will be deserialized from disk when removed from memory cache
--cache-memory-cache-unaffectedAdditionally cache computation of modules that are unchanged and reference only unchanged modules in memory
--no-cache-memory-cache-unaffectedNegative 'cache-memory-cache-unaffected' option
--cache-name <command>Name for the cache. Different names will lead to different coexisting caches
--cache-profileTrack and log detailed timing information for individual cache items
--no-cache-profileNegative 'cache-profile' option
--cache-store <command>When to store data to the filesystem. (pack: Store data when compiler is idle in a single file)
--cache-version <command>Version of the cache data. Different versions won't allow to reuse the cache and override existing content. Update the version when config changed in a way which doesn't allow to reuse cache. This will invalidate the cache
--context <command>The base directory (absolute path!) for resolving the `entry` option. If `output.pathinfo` is set, the included pathinfo is shortened to this directory
--dependencies <command...>References to another configuration to depend on
--dependencies-resetClear all items provided in 'dependencies' configuration. References to other configurations to depend on
--devtool,-d <command>Determine source maps to use
--no-devtoolDo not generate source maps
--entry <command...>The entry point(s) of your application e.g. ./src/main.js
--entry-resetClear all items provided in 'entry' configuration. All modules are loaded upon startup. The last one is exported
--experiments-async-web-assemblySupport WebAssembly as asynchronous EcmaScript Module
--no-experiments-async-web-assemblyNegative 'experiments-async-web-assembly' option
--experiments-back-compatEnable backward-compat layer with deprecation warnings for many webpack 4 APIs
--no-experiments-back-compatNegative 'experiments-back-compat' option
--experiments-build-http-allowed-uris <command...>Allowed URI pattern. Allowed URI (resp. the beginning of it)
--experiments-build-http-allowed-uris-resetClear all items provided in 'experiments.buildHttp.allowedUris' configuration. List of allowed URIs (resp. the beginning of them)
--experiments-build-http-cache-location <command>Location where resource content is stored for lockfile entries. It's also possible to disable storing by passing false
--no-experiments-build-http-cache-locationNegative 'experiments-build-http-cache-location' option
--experiments-build-http-frozenWhen set, anything that would lead to a modification of the lockfile or any resource content, will result in an error
--no-experiments-build-http-frozenNegative 'experiments-build-http-frozen' option
--experiments-build-http-lockfile-location <command>Location of the lockfile
--experiments-build-http-proxy <command>Proxy configuration, which can be used to specify a proxy server to use for HTTP requests
--experiments-build-http-upgradeWhen set, resources of existing lockfile entries will be fetched and entries will be upgraded when resource content has changed
--no-experiments-build-http-upgradeNegative 'experiments-build-http-upgrade' option
--experiments-cache-unaffectedEnable additional in memory caching of modules that are unchanged and reference only unchanged modules
--no-experiments-cache-unaffectedNegative 'experiments-cache-unaffected' option
--experiments-cssEnable css support
--no-experiments-cssNegative 'experiments-css' option
--experiments-css-exports-onlyAvoid generating and loading a stylesheet and only embed exports from css into output javascript files
--no-experiments-css-exports-onlyNegative 'experiments-css-exports-only' option
--experiments-future-defaultsApply defaults of next major version
--no-experiments-future-defaultsNegative 'experiments-future-defaults' option
--experiments-layersEnable module layers
--no-experiments-layersNegative 'experiments-layers' option
--experiments-lazy-compilationCompile entrypoints and import()s only when they are accessed
--no-experiments-lazy-compilationNegative 'experiments-lazy-compilation' option
--experiments-lazy-compilation-backend-client <command>A custom client
--experiments-lazy-compilation-backend-listen <command>A port
--experiments-lazy-compilation-backend-listen-host <command>A host
--experiments-lazy-compilation-backend-listen-port <command>A port
--experiments-lazy-compilation-backend-protocol <command>Specifies the protocol the client should use to connect to the server
--experiments-lazy-compilation-entriesEnable/disable lazy compilation for entries
--no-experiments-lazy-compilation-entriesNegative 'experiments-lazy-compilation-entries' option
--experiments-lazy-compilation-importsEnable/disable lazy compilation for import() modules
--no-experiments-lazy-compilation-importsNegative 'experiments-lazy-compilation-imports' option
--experiments-lazy-compilation-test <command>Specify which entrypoints or import()ed modules should be lazily compiled. This is matched with the imported module and not the entrypoint name
--experiments-output-moduleAllow output javascript files as module source type
--no-experiments-output-moduleNegative 'experiments-output-module' option
--experiments-sync-web-assemblySupport WebAssembly as synchronous EcmaScript Module (outdated)
--no-experiments-sync-web-assemblyNegative 'experiments-sync-web-assembly' option
--experiments-top-level-awaitAllow using top-level-await in EcmaScript Modules
--no-experiments-top-level-awaitNegative 'experiments-top-level-await' option
--externals <command...>Every matched dependency becomes external. An exact matched dependency becomes external. The same string is used as external dependency
--externals-resetClear all items provided in 'externals' configuration. Specify dependencies that shouldn't be resolved by webpack, but should become dependencies of the resulting bundle. The kind of the dependency depends on `output.libraryTarget`
--externals-presets-electronTreat common electron built-in modules in main and preload context like 'electron', 'ipc' or 'shell' as external and load them via require() when used
--no-externals-presets-electronNegative 'externals-presets-electron' option
--externals-presets-electron-mainTreat electron built-in modules in the main context like 'app', 'ipc-main' or 'shell' as external and load them via require() when used
--no-externals-presets-electron-mainNegative 'externals-presets-electron-main' option
--externals-presets-electron-preloadTreat electron built-in modules in the preload context like 'web-frame', 'ipc-renderer' or 'shell' as external and load them via require() when used
--no-externals-presets-electron-preloadNegative 'externals-presets-electron-preload' option
--externals-presets-electron-rendererTreat electron built-in modules in the renderer context like 'web-frame', 'ipc-renderer' or 'shell' as external and load them via require() when used
--no-externals-presets-electron-rendererNegative 'externals-presets-electron-renderer' option
--externals-presets-nodeTreat node.js built-in modules like fs, path or vm as external and load them via require() when used
--no-externals-presets-nodeNegative 'externals-presets-node' option
--externals-presets-nwjsTreat NW.js legacy nw.gui module as external and load it via require() when used
--no-externals-presets-nwjsNegative 'externals-presets-nwjs' option
--externals-presets-webTreat references to 'http(s)://...' and 'std:...' as external and load them via import when used (Note that this changes execution order as externals are executed before any other code in the chunk)
--no-externals-presets-webNegative 'externals-presets-web' option
--externals-presets-web-asyncTreat references to 'http(s)://...' and 'std:...' as external and load them via async import() when used (Note that this external type is an async module, which has various effects on the execution)
--no-externals-presets-web-asyncNegative 'externals-presets-web-async' option
--externals-type <command>Specifies the default type of externals ('amd*', 'umd*', 'system' and 'jsonp' depend on output.libraryTarget set to the same value)
--ignore-warnings <command...>A RegExp to select the warning message
--ignore-warnings-file <command...>A RegExp to select the origin file for the warning
--ignore-warnings-message <command...>A RegExp to select the warning message
--ignore-warnings-module <command...>A RegExp to select the origin module for the warning
--ignore-warnings-resetClear all items provided in 'ignoreWarnings' configuration. Ignore specific warnings
--infrastructure-logging-append-onlyOnly appends lines to the output. Avoids updating existing output e. g. for status messages. This option is only used when no custom console is provided
--no-infrastructure-logging-append-onlyNegative 'infrastructure-logging-append-only' option
--infrastructure-logging-colorsEnables/Disables colorful output. This option is only used when no custom console is provided
--no-infrastructure-logging-colorsNegative 'infrastructure-logging-colors' option
--infrastructure-logging-debug [command...]Enable/Disable debug logging for all loggers. Enable debug logging for specific loggers
--no-infrastructure-logging-debugNegative 'infrastructure-logging-debug' option
--infrastructure-logging-debug-resetClear all items provided in 'infrastructureLogging.debug' configuration. Enable debug logging for specific loggers
--infrastructure-logging-level <command>Log level
--mode <command>Defines the mode to pass to webpack
--module-expr-context-criticalEnable warnings for full dynamic dependencies
--no-module-expr-context-criticalNegative 'module-expr-context-critical' option
--module-expr-context-recursiveEnable recursive directory lookup for full dynamic dependencies. Deprecated: This option has moved to 'module.parser.javascript.exprContextRecursive'
--no-module-expr-context-recursiveNegative 'module-expr-context-recursive' option
--module-expr-context-reg-exp [command]Sets the default regular expression for full dynamic dependencies. Deprecated: This option has moved to 'module.parser.javascript.exprContextRegExp'
--no-module-expr-context-reg-expNegative 'module-expr-context-reg-exp' option
--module-expr-context-request <command>Set the default request for full dynamic dependencies. Deprecated: This option has moved to 'module.parser.javascript.exprContextRequest'
--module-generator-asset-data-url-encoding <command>Asset encoding (defaults to base64)
--no-module-generator-asset-data-url-encodingNegative 'module-generator-asset-data-url-encoding' option
--module-generator-asset-data-url-mimetype <command>Asset mimetype (getting from file extension by default)
--module-generator-asset-emitEmit an output asset from this asset module. This can be set to 'false' to omit emitting e. g. for SSR
--no-module-generator-asset-emitNegative 'module-generator-asset-emit' option
--module-generator-asset-filename <command>Specifies the filename template of output files on disk. You must **not** specify an absolute path here, but the path may contain folders separated by '/'! The specified path is joined with the value of the 'output.path' option to determine the location on disk
--module-generator-asset-output-path <command>Emit the asset in the specified folder relative to 'output.path'. This should only be needed when custom 'publicPath' is specified to match the folder structure there
--module-generator-asset-public-path <command>The 'publicPath' specifies the public URL address of the output files when referenced in a browser
--module-generator-asset-inline-data-url-encoding <command>Asset encoding (defaults to base64)
--no-module-generator-asset-inline-data-url-encodingNegative 'module-generator-asset-inline-data-url-encoding' option
--module-generator-asset-inline-data-url-mimetype <command>Asset mimetype (getting from file extension by default)
--module-generator-asset-resource-emitEmit an output asset from this asset module. This can be set to 'false' to omit emitting e. g. for SSR
--no-module-generator-asset-resource-emitNegative 'module-generator-asset-resource-emit' option
--module-generator-asset-resource-filename <command>Specifies the filename template of output files on disk. You must **not** specify an absolute path here, but the path may contain folders separated by '/'! The specified path is joined with the value of the 'output.path' option to determine the location on disk
--module-generator-asset-resource-output-path <command>Emit the asset in the specified folder relative to 'output.path'. This should only be needed when custom 'publicPath' is specified to match the folder structure there
--module-generator-asset-resource-public-path <command>The 'publicPath' specifies the public URL address of the output files when referenced in a browser
--module-no-parse <command...>A regular expression, when matched the module is not parsed. An absolute path, when the module starts with this path it is not parsed
--module-no-parse-resetClear all items provided in 'module.noParse' configuration. Don't parse files matching. It's matched against the full resolved request
--module-parser-asset-data-url-condition-max-size <command>Maximum size of asset that should be inline as modules. Default: 8kb
--no-module-parser-javascript-amdNegative 'module-parser-javascript-amd' option
--module-parser-javascript-browserifyEnable/disable special handling for browserify bundles
--no-module-parser-javascript-browserifyNegative 'module-parser-javascript-browserify' option
--module-parser-javascript-commonjsEnable/disable parsing of CommonJs syntax
--no-module-parser-javascript-commonjsNegative 'module-parser-javascript-commonjs' option
--module-parser-javascript-commonjs-magic-commentsEnable/disable parsing of magic comments in CommonJs syntax
--no-module-parser-javascript-commonjs-magic-commentsNegative 'module-parser-javascript-commonjs-magic-comments' option
--module-parser-javascript-exports-presence <command>Specifies the behavior of invalid export names in "import ... from ..." and "export ... from ..."
--no-module-parser-javascript-exports-presenceNegative 'module-parser-javascript-exports-presence' option
--module-parser-javascript-expr-context-criticalEnable warnings for full dynamic dependencies
--no-module-parser-javascript-expr-context-criticalNegative 'module-parser-javascript-expr-context-critical' option
--module-parser-javascript-expr-context-recursiveEnable recursive directory lookup for full dynamic dependencies
--no-module-parser-javascript-expr-context-recursiveNegative 'module-parser-javascript-expr-context-recursive' option
--module-parser-javascript-expr-context-reg-exp [command]Sets the default regular expression for full dynamic dependencies
--no-module-parser-javascript-expr-context-reg-expNegative 'module-parser-javascript-expr-context-reg-exp' option
--module-parser-javascript-expr-context-request <command>Set the default request for full dynamic dependencies
--module-parser-javascript-harmonyEnable/disable parsing of EcmaScript Modules syntax
--no-module-parser-javascript-harmonyNegative 'module-parser-javascript-harmony' option
--module-parser-javascript-importEnable/disable parsing of import() syntax
--no-module-parser-javascript-importNegative 'module-parser-javascript-import' option
--module-parser-javascript-import-exports-presence <command>Specifies the behavior of invalid export names in "import ... from ..."
--no-module-parser-javascript-import-exports-presenceNegative 'module-parser-javascript-import-exports-presence' option
--module-parser-javascript-import-metaEnable/disable evaluating import.meta
--no-module-parser-javascript-import-metaNegative 'module-parser-javascript-import-meta' option
--module-parser-javascript-import-meta-contextEnable/disable evaluating import.meta.webpackContext
--no-module-parser-javascript-import-meta-contextNegative 'module-parser-javascript-import-meta-context' option
--no-module-parser-javascript-nodeNegative 'module-parser-javascript-node' option
--module-parser-javascript-node-dirname [command]Include a polyfill for the '__dirname' variable
--no-module-parser-javascript-node-dirnameNegative 'module-parser-javascript-node-dirname' option
--module-parser-javascript-node-filename [command]Include a polyfill for the '__filename' variable
--no-module-parser-javascript-node-filenameNegative 'module-parser-javascript-node-filename' option
--module-parser-javascript-node-global [command]Include a polyfill for the 'global' variable
--no-module-parser-javascript-node-globalNegative 'module-parser-javascript-node-global' option
--module-parser-javascript-reexport-exports-presence <command>Specifies the behavior of invalid export names in "export ... from ...". This might be useful to disable during the migration from "export ... from ..." to "export type ... from ..." when reexporting types in TypeScript
--no-module-parser-javascript-reexport-exports-presenceNegative 'module-parser-javascript-reexport-exports-presence' option
--module-parser-javascript-require-contextEnable/disable parsing of require.context syntax
--no-module-parser-javascript-require-contextNegative 'module-parser-javascript-require-context' option
--module-parser-javascript-require-ensureEnable/disable parsing of require.ensure syntax
--no-module-parser-javascript-require-ensureNegative 'module-parser-javascript-require-ensure' option
--module-parser-javascript-require-includeEnable/disable parsing of require.include syntax
--no-module-parser-javascript-require-includeNegative 'module-parser-javascript-require-include' option
--module-parser-javascript-require-jsEnable/disable parsing of require.js special syntax like require.config, requirejs.config, require.version and requirejs.onError
--no-module-parser-javascript-require-jsNegative 'module-parser-javascript-require-js' option
--module-parser-javascript-strict-export-presenceDeprecated in favor of "exportsPresence". Emit errors instead of warnings when imported names don't exist in imported module
--no-module-parser-javascript-strict-export-presenceNegative 'module-parser-javascript-strict-export-presence' option
--module-parser-javascript-strict-this-context-on-importsHandle the this context correctly according to the spec for namespace objects
--no-module-parser-javascript-strict-this-context-on-importsNegative 'module-parser-javascript-strict-this-context-on-imports' option
--module-parser-javascript-systemEnable/disable parsing of System.js special syntax like System.import, System.get, System.set and System.register
--no-module-parser-javascript-systemNegative 'module-parser-javascript-system' option
--module-parser-javascript-unknown-context-criticalEnable warnings when using the require function in a not statically analyse-able way
--no-module-parser-javascript-unknown-context-criticalNegative 'module-parser-javascript-unknown-context-critical' option
--module-parser-javascript-unknown-context-recursiveEnable recursive directory lookup when using the require function in a not statically analyse-able way
--no-module-parser-javascript-unknown-context-recursiveNegative 'module-parser-javascript-unknown-context-recursive' option
--module-parser-javascript-unknown-context-reg-exp [command]Sets the regular expression when using the require function in a not statically analyse-able way
--no-module-parser-javascript-unknown-context-reg-expNegative 'module-parser-javascript-unknown-context-reg-exp' option
--module-parser-javascript-unknown-context-request <command>Sets the request when using the require function in a not statically analyse-able way
--module-parser-javascript-url [command]Enable/disable parsing of new URL() syntax
--no-module-parser-javascript-urlNegative 'module-parser-javascript-url' option
--module-parser-javascript-worker [command...]Specify a syntax that should be parsed as WebWorker reference. 'Abc' handles 'new Abc()', 'Abc from xyz' handles 'import { Abc } from "xyz"; new Abc()', 'abc()' handles 'abc()', and combinations are also possible. Disable or configure parsing of WebWorker syntax like new Worker() or navigator.serviceWorker.register()
--no-module-parser-javascript-workerNegative 'module-parser-javascript-worker' option
--module-parser-javascript-worker-resetClear all items provided in 'module.parser.javascript.worker' configuration. Disable or configure parsing of WebWorker syntax like new Worker() or navigator.serviceWorker.register()
--module-parser-javascript-wrapped-context-criticalEnable warnings for partial dynamic dependencies
--no-module-parser-javascript-wrapped-context-criticalNegative 'module-parser-javascript-wrapped-context-critical' option
--module-parser-javascript-wrapped-context-recursiveEnable recursive directory lookup for partial dynamic dependencies
--no-module-parser-javascript-wrapped-context-recursiveNegative 'module-parser-javascript-wrapped-context-recursive' option
--module-parser-javascript-wrapped-context-reg-exp <command>Set the inner regular expression for partial dynamic dependencies
--no-module-parser-javascript-auto-amdNegative 'module-parser-javascript-auto-amd' option
--module-parser-javascript-auto-browserifyEnable/disable special handling for browserify bundles
--no-module-parser-javascript-auto-browserifyNegative 'module-parser-javascript-auto-browserify' option
--module-parser-javascript-auto-commonjsEnable/disable parsing of CommonJs syntax
--no-module-parser-javascript-auto-commonjsNegative 'module-parser-javascript-auto-commonjs' option
--module-parser-javascript-auto-commonjs-magic-commentsEnable/disable parsing of magic comments in CommonJs syntax
--no-module-parser-javascript-auto-commonjs-magic-commentsNegative 'module-parser-javascript-auto-commonjs-magic-comments' option
--module-parser-javascript-auto-exports-presence <command>Specifies the behavior of invalid export names in "import ... from ..." and "export ... from ..."
--no-module-parser-javascript-auto-exports-presenceNegative 'module-parser-javascript-auto-exports-presence' option
--module-parser-javascript-auto-expr-context-criticalEnable warnings for full dynamic dependencies
--no-module-parser-javascript-auto-expr-context-criticalNegative 'module-parser-javascript-auto-expr-context-critical' option
--module-parser-javascript-auto-expr-context-recursiveEnable recursive directory lookup for full dynamic dependencies
--no-module-parser-javascript-auto-expr-context-recursiveNegative 'module-parser-javascript-auto-expr-context-recursive' option
--module-parser-javascript-auto-expr-context-reg-exp [command]Sets the default regular expression for full dynamic dependencies
--no-module-parser-javascript-auto-expr-context-reg-expNegative 'module-parser-javascript-auto-expr-context-reg-exp' option
--module-parser-javascript-auto-expr-context-request <command>Set the default request for full dynamic dependencies
--module-parser-javascript-auto-harmonyEnable/disable parsing of EcmaScript Modules syntax
--no-module-parser-javascript-auto-harmonyNegative 'module-parser-javascript-auto-harmony' option
--module-parser-javascript-auto-importEnable/disable parsing of import() syntax
--no-module-parser-javascript-auto-importNegative 'module-parser-javascript-auto-import' option
--module-parser-javascript-auto-import-exports-presence <command>Specifies the behavior of invalid export names in "import ... from ..."
--no-module-parser-javascript-auto-import-exports-presenceNegative 'module-parser-javascript-auto-import-exports-presence' option
--module-parser-javascript-auto-import-metaEnable/disable evaluating import.meta
--no-module-parser-javascript-auto-import-metaNegative 'module-parser-javascript-auto-import-meta' option
--module-parser-javascript-auto-import-meta-contextEnable/disable evaluating import.meta.webpackContext
--no-module-parser-javascript-auto-import-meta-contextNegative 'module-parser-javascript-auto-import-meta-context' option
--no-module-parser-javascript-auto-nodeNegative 'module-parser-javascript-auto-node' option
--module-parser-javascript-auto-node-dirname [command]Include a polyfill for the '__dirname' variable
--no-module-parser-javascript-auto-node-dirnameNegative 'module-parser-javascript-auto-node-dirname' option
--module-parser-javascript-auto-node-filename [command]Include a polyfill for the '__filename' variable
--no-module-parser-javascript-auto-node-filenameNegative 'module-parser-javascript-auto-node-filename' option
--module-parser-javascript-auto-node-global [command]Include a polyfill for the 'global' variable
--no-module-parser-javascript-auto-node-globalNegative 'module-parser-javascript-auto-node-global' option
--module-parser-javascript-auto-reexport-exports-presence <command>Specifies the behavior of invalid export names in "export ... from ...". This might be useful to disable during the migration from "export ... from ..." to "export type ... from ..." when reexporting types in TypeScript
--no-module-parser-javascript-auto-reexport-exports-presenceNegative 'module-parser-javascript-auto-reexport-exports-presence' option
--module-parser-javascript-auto-require-contextEnable/disable parsing of require.context syntax
--no-module-parser-javascript-auto-require-contextNegative 'module-parser-javascript-auto-require-context' option
--module-parser-javascript-auto-require-ensureEnable/disable parsing of require.ensure syntax
--no-module-parser-javascript-auto-require-ensureNegative 'module-parser-javascript-auto-require-ensure' option
--module-parser-javascript-auto-require-includeEnable/disable parsing of require.include syntax
--no-module-parser-javascript-auto-require-includeNegative 'module-parser-javascript-auto-require-include' option
--module-parser-javascript-auto-require-jsEnable/disable parsing of require.js special syntax like require.config, requirejs.config, require.version and requirejs.onError
--no-module-parser-javascript-auto-require-jsNegative 'module-parser-javascript-auto-require-js' option
--module-parser-javascript-auto-strict-export-presenceDeprecated in favor of "exportsPresence". Emit errors instead of warnings when imported names don't exist in imported module
--no-module-parser-javascript-auto-strict-export-presenceNegative 'module-parser-javascript-auto-strict-export-presence' option
--module-parser-javascript-auto-strict-this-context-on-importsHandle the this context correctly according to the spec for namespace objects
--no-module-parser-javascript-auto-strict-this-context-on-importsNegative 'module-parser-javascript-auto-strict-this-context-on-imports' option
--module-parser-javascript-auto-systemEnable/disable parsing of System.js special syntax like System.import, System.get, System.set and System.register
--no-module-parser-javascript-auto-systemNegative 'module-parser-javascript-auto-system' option
--module-parser-javascript-auto-unknown-context-criticalEnable warnings when using the require function in a not statically analyse-able way
--no-module-parser-javascript-auto-unknown-context-criticalNegative 'module-parser-javascript-auto-unknown-context-critical' option
--module-parser-javascript-auto-unknown-context-recursiveEnable recursive directory lookup when using the require function in a not statically analyse-able way
--no-module-parser-javascript-auto-unknown-context-recursiveNegative 'module-parser-javascript-auto-unknown-context-recursive' option
--module-parser-javascript-auto-unknown-context-reg-exp [command]Sets the regular expression when using the require function in a not statically analyse-able way
--no-module-parser-javascript-auto-unknown-context-reg-expNegative 'module-parser-javascript-auto-unknown-context-reg-exp' option
--module-parser-javascript-auto-unknown-context-request <command>Sets the request when using the require function in a not statically analyse-able way
--module-parser-javascript-auto-url [command]Enable/disable parsing of new URL() syntax
--no-module-parser-javascript-auto-urlNegative 'module-parser-javascript-auto-url' option
--module-parser-javascript-auto-worker [command...]Specify a syntax that should be parsed as WebWorker reference. 'Abc' handles 'new Abc()', 'Abc from xyz' handles 'import { Abc } from "xyz"; new Abc()', 'abc()' handles 'abc()', and combinations are also possible. Disable or configure parsing of WebWorker syntax like new Worker() or navigator.serviceWorker.register()
--no-module-parser-javascript-auto-workerNegative 'module-parser-javascript-auto-worker' option
--module-parser-javascript-auto-worker-resetClear all items provided in 'module.parser.javascript/auto.worker' configuration. Disable or configure parsing of WebWorker syntax like new Worker() or navigator.serviceWorker.register()
--module-parser-javascript-auto-wrapped-context-criticalEnable warnings for partial dynamic dependencies
--no-module-parser-javascript-auto-wrapped-context-criticalNegative 'module-parser-javascript-auto-wrapped-context-critical' option
--module-parser-javascript-auto-wrapped-context-recursiveEnable recursive directory lookup for partial dynamic dependencies
--no-module-parser-javascript-auto-wrapped-context-recursiveNegative 'module-parser-javascript-auto-wrapped-context-recursive' option
--module-parser-javascript-auto-wrapped-context-reg-exp <command>Set the inner regular expression for partial dynamic dependencies
--no-module-parser-javascript-dynamic-amdNegative 'module-parser-javascript-dynamic-amd' option
--module-parser-javascript-dynamic-browserifyEnable/disable special handling for browserify bundles
--no-module-parser-javascript-dynamic-browserifyNegative 'module-parser-javascript-dynamic-browserify' option
--module-parser-javascript-dynamic-commonjsEnable/disable parsing of CommonJs syntax
--no-module-parser-javascript-dynamic-commonjsNegative 'module-parser-javascript-dynamic-commonjs' option
--module-parser-javascript-dynamic-commonjs-magic-commentsEnable/disable parsing of magic comments in CommonJs syntax
--no-module-parser-javascript-dynamic-commonjs-magic-commentsNegative 'module-parser-javascript-dynamic-commonjs-magic-comments' option
--module-parser-javascript-dynamic-exports-presence <command>Specifies the behavior of invalid export names in "import ... from ..." and "export ... from ..."
--no-module-parser-javascript-dynamic-exports-presenceNegative 'module-parser-javascript-dynamic-exports-presence' option
--module-parser-javascript-dynamic-expr-context-criticalEnable warnings for full dynamic dependencies
--no-module-parser-javascript-dynamic-expr-context-criticalNegative 'module-parser-javascript-dynamic-expr-context-critical' option
--module-parser-javascript-dynamic-expr-context-recursiveEnable recursive directory lookup for full dynamic dependencies
--no-module-parser-javascript-dynamic-expr-context-recursiveNegative 'module-parser-javascript-dynamic-expr-context-recursive' option
--module-parser-javascript-dynamic-expr-context-reg-exp [command]Sets the default regular expression for full dynamic dependencies
--no-module-parser-javascript-dynamic-expr-context-reg-expNegative 'module-parser-javascript-dynamic-expr-context-reg-exp' option
--module-parser-javascript-dynamic-expr-context-request <command>Set the default request for full dynamic dependencies
--module-parser-javascript-dynamic-harmonyEnable/disable parsing of EcmaScript Modules syntax
--no-module-parser-javascript-dynamic-harmonyNegative 'module-parser-javascript-dynamic-harmony' option
--module-parser-javascript-dynamic-importEnable/disable parsing of import() syntax
--no-module-parser-javascript-dynamic-importNegative 'module-parser-javascript-dynamic-import' option
--module-parser-javascript-dynamic-import-exports-presence <command>Specifies the behavior of invalid export names in "import ... from ..."
--no-module-parser-javascript-dynamic-import-exports-presenceNegative 'module-parser-javascript-dynamic-import-exports-presence' option
--module-parser-javascript-dynamic-import-metaEnable/disable evaluating import.meta
--no-module-parser-javascript-dynamic-import-metaNegative 'module-parser-javascript-dynamic-import-meta' option
--module-parser-javascript-dynamic-import-meta-contextEnable/disable evaluating import.meta.webpackContext
--no-module-parser-javascript-dynamic-import-meta-contextNegative 'module-parser-javascript-dynamic-import-meta-context' option
--no-module-parser-javascript-dynamic-nodeNegative 'module-parser-javascript-dynamic-node' option
--module-parser-javascript-dynamic-node-dirname [command]Include a polyfill for the '__dirname' variable
--no-module-parser-javascript-dynamic-node-dirnameNegative 'module-parser-javascript-dynamic-node-dirname' option
--module-parser-javascript-dynamic-node-filename [command]Include a polyfill for the '__filename' variable
--no-module-parser-javascript-dynamic-node-filenameNegative 'module-parser-javascript-dynamic-node-filename' option
--module-parser-javascript-dynamic-node-global [command]Include a polyfill for the 'global' variable
--no-module-parser-javascript-dynamic-node-globalNegative 'module-parser-javascript-dynamic-node-global' option
--module-parser-javascript-dynamic-reexport-exports-presence <command>Specifies the behavior of invalid export names in "export ... from ...". This might be useful to disable during the migration from "export ... from ..." to "export type ... from ..." when reexporting types in TypeScript
--no-module-parser-javascript-dynamic-reexport-exports-presenceNegative 'module-parser-javascript-dynamic-reexport-exports-presence' option
--module-parser-javascript-dynamic-require-contextEnable/disable parsing of require.context syntax
--no-module-parser-javascript-dynamic-require-contextNegative 'module-parser-javascript-dynamic-require-context' option
--module-parser-javascript-dynamic-require-ensureEnable/disable parsing of require.ensure syntax
--no-module-parser-javascript-dynamic-require-ensureNegative 'module-parser-javascript-dynamic-require-ensure' option
--module-parser-javascript-dynamic-require-includeEnable/disable parsing of require.include syntax
--no-module-parser-javascript-dynamic-require-includeNegative 'module-parser-javascript-dynamic-require-include' option
--module-parser-javascript-dynamic-require-jsEnable/disable parsing of require.js special syntax like require.config, requirejs.config, require.version and requirejs.onError
--no-module-parser-javascript-dynamic-require-jsNegative 'module-parser-javascript-dynamic-require-js' option
--module-parser-javascript-dynamic-strict-export-presenceDeprecated in favor of "exportsPresence". Emit errors instead of warnings when imported names don't exist in imported module
--no-module-parser-javascript-dynamic-strict-export-presenceNegative 'module-parser-javascript-dynamic-strict-export-presence' option
--module-parser-javascript-dynamic-strict-this-context-on-importsHandle the this context correctly according to the spec for namespace objects
--no-module-parser-javascript-dynamic-strict-this-context-on-importsNegative 'module-parser-javascript-dynamic-strict-this-context-on-imports' option
--module-parser-javascript-dynamic-systemEnable/disable parsing of System.js special syntax like System.import, System.get, System.set and System.register
--no-module-parser-javascript-dynamic-systemNegative 'module-parser-javascript-dynamic-system' option
--module-parser-javascript-dynamic-unknown-context-criticalEnable warnings when using the require function in a not statically analyse-able way
--no-module-parser-javascript-dynamic-unknown-context-criticalNegative 'module-parser-javascript-dynamic-unknown-context-critical' option
--module-parser-javascript-dynamic-unknown-context-recursiveEnable recursive directory lookup when using the require function in a not statically analyse-able way
--no-module-parser-javascript-dynamic-unknown-context-recursiveNegative 'module-parser-javascript-dynamic-unknown-context-recursive' option
--module-parser-javascript-dynamic-unknown-context-reg-exp [command]Sets the regular expression when using the require function in a not statically analyse-able way
--no-module-parser-javascript-dynamic-unknown-context-reg-expNegative 'module-parser-javascript-dynamic-unknown-context-reg-exp' option
--module-parser-javascript-dynamic-unknown-context-request <command>Sets the request when using the require function in a not statically analyse-able way
--module-parser-javascript-dynamic-url [command]Enable/disable parsing of new URL() syntax
--no-module-parser-javascript-dynamic-urlNegative 'module-parser-javascript-dynamic-url' option
--module-parser-javascript-dynamic-worker [command...]Specify a syntax that should be parsed as WebWorker reference. 'Abc' handles 'new Abc()', 'Abc from xyz' handles 'import { Abc } from "xyz"; new Abc()', 'abc()' handles 'abc()', and combinations are also possible. Disable or configure parsing of WebWorker syntax like new Worker() or navigator.serviceWorker.register()
--no-module-parser-javascript-dynamic-workerNegative 'module-parser-javascript-dynamic-worker' option
--module-parser-javascript-dynamic-worker-resetClear all items provided in 'module.parser.javascript/dynamic.worker' configuration. Disable or configure parsing of WebWorker syntax like new Worker() or navigator.serviceWorker.register()
--module-parser-javascript-dynamic-wrapped-context-criticalEnable warnings for partial dynamic dependencies
--no-module-parser-javascript-dynamic-wrapped-context-criticalNegative 'module-parser-javascript-dynamic-wrapped-context-critical' option
--module-parser-javascript-dynamic-wrapped-context-recursiveEnable recursive directory lookup for partial dynamic dependencies
--no-module-parser-javascript-dynamic-wrapped-context-recursiveNegative 'module-parser-javascript-dynamic-wrapped-context-recursive' option
--module-parser-javascript-dynamic-wrapped-context-reg-exp <command>Set the inner regular expression for partial dynamic dependencies
--no-module-parser-javascript-esm-amdNegative 'module-parser-javascript-esm-amd' option
--module-parser-javascript-esm-browserifyEnable/disable special handling for browserify bundles
--no-module-parser-javascript-esm-browserifyNegative 'module-parser-javascript-esm-browserify' option
--module-parser-javascript-esm-commonjsEnable/disable parsing of CommonJs syntax
--no-module-parser-javascript-esm-commonjsNegative 'module-parser-javascript-esm-commonjs' option
--module-parser-javascript-esm-commonjs-magic-commentsEnable/disable parsing of magic comments in CommonJs syntax
--no-module-parser-javascript-esm-commonjs-magic-commentsNegative 'module-parser-javascript-esm-commonjs-magic-comments' option
--module-parser-javascript-esm-exports-presence <command>Specifies the behavior of invalid export names in "import ... from ..." and "export ... from ..."
--no-module-parser-javascript-esm-exports-presenceNegative 'module-parser-javascript-esm-exports-presence' option
--module-parser-javascript-esm-expr-context-criticalEnable warnings for full dynamic dependencies
--no-module-parser-javascript-esm-expr-context-criticalNegative 'module-parser-javascript-esm-expr-context-critical' option
--module-parser-javascript-esm-expr-context-recursiveEnable recursive directory lookup for full dynamic dependencies
--no-module-parser-javascript-esm-expr-context-recursiveNegative 'module-parser-javascript-esm-expr-context-recursive' option
--module-parser-javascript-esm-expr-context-reg-exp [command]Sets the default regular expression for full dynamic dependencies
--no-module-parser-javascript-esm-expr-context-reg-expNegative 'module-parser-javascript-esm-expr-context-reg-exp' option
--module-parser-javascript-esm-expr-context-request <command>Set the default request for full dynamic dependencies
--module-parser-javascript-esm-harmonyEnable/disable parsing of EcmaScript Modules syntax
--no-module-parser-javascript-esm-harmonyNegative 'module-parser-javascript-esm-harmony' option
--module-parser-javascript-esm-importEnable/disable parsing of import() syntax
--no-module-parser-javascript-esm-importNegative 'module-parser-javascript-esm-import' option
--module-parser-javascript-esm-import-exports-presence <command>Specifies the behavior of invalid export names in "import ... from ..."
--no-module-parser-javascript-esm-import-exports-presenceNegative 'module-parser-javascript-esm-import-exports-presence' option
--module-parser-javascript-esm-import-metaEnable/disable evaluating import.meta
--no-module-parser-javascript-esm-import-metaNegative 'module-parser-javascript-esm-import-meta' option
--module-parser-javascript-esm-import-meta-contextEnable/disable evaluating import.meta.webpackContext
--no-module-parser-javascript-esm-import-meta-contextNegative 'module-parser-javascript-esm-import-meta-context' option
--no-module-parser-javascript-esm-nodeNegative 'module-parser-javascript-esm-node' option
--module-parser-javascript-esm-node-dirname [command]Include a polyfill for the '__dirname' variable
--no-module-parser-javascript-esm-node-dirnameNegative 'module-parser-javascript-esm-node-dirname' option
--module-parser-javascript-esm-node-filename [command]Include a polyfill for the '__filename' variable
--no-module-parser-javascript-esm-node-filenameNegative 'module-parser-javascript-esm-node-filename' option
--module-parser-javascript-esm-node-global [command]Include a polyfill for the 'global' variable
--no-module-parser-javascript-esm-node-globalNegative 'module-parser-javascript-esm-node-global' option
--module-parser-javascript-esm-reexport-exports-presence <command>Specifies the behavior of invalid export names in "export ... from ...". This might be useful to disable during the migration from "export ... from ..." to "export type ... from ..." when reexporting types in TypeScript
--no-module-parser-javascript-esm-reexport-exports-presenceNegative 'module-parser-javascript-esm-reexport-exports-presence' option
--module-parser-javascript-esm-require-contextEnable/disable parsing of require.context syntax
--no-module-parser-javascript-esm-require-contextNegative 'module-parser-javascript-esm-require-context' option
--module-parser-javascript-esm-require-ensureEnable/disable parsing of require.ensure syntax
--no-module-parser-javascript-esm-require-ensureNegative 'module-parser-javascript-esm-require-ensure' option
--module-parser-javascript-esm-require-includeEnable/disable parsing of require.include syntax
--no-module-parser-javascript-esm-require-includeNegative 'module-parser-javascript-esm-require-include' option
--module-parser-javascript-esm-require-jsEnable/disable parsing of require.js special syntax like require.config, requirejs.config, require.version and requirejs.onError
--no-module-parser-javascript-esm-require-jsNegative 'module-parser-javascript-esm-require-js' option
--module-parser-javascript-esm-strict-export-presenceDeprecated in favor of "exportsPresence". Emit errors instead of warnings when imported names don't exist in imported module
--no-module-parser-javascript-esm-strict-export-presenceNegative 'module-parser-javascript-esm-strict-export-presence' option
--module-parser-javascript-esm-strict-this-context-on-importsHandle the this context correctly according to the spec for namespace objects
--no-module-parser-javascript-esm-strict-this-context-on-importsNegative 'module-parser-javascript-esm-strict-this-context-on-imports' option
--module-parser-javascript-esm-systemEnable/disable parsing of System.js special syntax like System.import, System.get, System.set and System.register
--no-module-parser-javascript-esm-systemNegative 'module-parser-javascript-esm-system' option
--module-parser-javascript-esm-unknown-context-criticalEnable warnings when using the require function in a not statically analyse-able way
--no-module-parser-javascript-esm-unknown-context-criticalNegative 'module-parser-javascript-esm-unknown-context-critical' option
--module-parser-javascript-esm-unknown-context-recursiveEnable recursive directory lookup when using the require function in a not statically analyse-able way
--no-module-parser-javascript-esm-unknown-context-recursiveNegative 'module-parser-javascript-esm-unknown-context-recursive' option
--module-parser-javascript-esm-unknown-context-reg-exp [command]Sets the regular expression when using the require function in a not statically analyse-able way
--no-module-parser-javascript-esm-unknown-context-reg-expNegative 'module-parser-javascript-esm-unknown-context-reg-exp' option
--module-parser-javascript-esm-unknown-context-request <command>Sets the request when using the require function in a not statically analyse-able way
--module-parser-javascript-esm-url [command]Enable/disable parsing of new URL() syntax
--no-module-parser-javascript-esm-urlNegative 'module-parser-javascript-esm-url' option
--module-parser-javascript-esm-worker [command...]Specify a syntax that should be parsed as WebWorker reference. 'Abc' handles 'new Abc()', 'Abc from xyz' handles 'import { Abc } from "xyz"; new Abc()', 'abc()' handles 'abc()', and combinations are also possible. Disable or configure parsing of WebWorker syntax like new Worker() or navigator.serviceWorker.register()
--no-module-parser-javascript-esm-workerNegative 'module-parser-javascript-esm-worker' option
--module-parser-javascript-esm-worker-resetClear all items provided in 'module.parser.javascript/esm.worker' configuration. Disable or configure parsing of WebWorker syntax like new Worker() or navigator.serviceWorker.register()
--module-parser-javascript-esm-wrapped-context-criticalEnable warnings for partial dynamic dependencies
--no-module-parser-javascript-esm-wrapped-context-criticalNegative 'module-parser-javascript-esm-wrapped-context-critical' option
--module-parser-javascript-esm-wrapped-context-recursiveEnable recursive directory lookup for partial dynamic dependencies
--no-module-parser-javascript-esm-wrapped-context-recursiveNegative 'module-parser-javascript-esm-wrapped-context-recursive' option
--module-parser-javascript-esm-wrapped-context-reg-exp <command>Set the inner regular expression for partial dynamic dependencies
--module-rules-compiler <command...>Match the child compiler name
--module-rules-compiler-not <command...>Logical NOT
--module-rules-dependency <command...>Match dependency type
--module-rules-dependency-not <command...>Logical NOT
--module-rules-enforce <command...>Enforce this rule as pre or post step
--module-rules-exclude <command...>Shortcut for resource.exclude
--module-rules-exclude-not <command...>Logical NOT
--module-rules-include <command...>Shortcut for resource.include
--module-rules-include-not <command...>Logical NOT
--module-rules-issuer <command...>Match the issuer of the module (The module pointing to this module)
--module-rules-issuer-not <command...>Logical NOT
--module-rules-issuer-layer <command...>Match layer of the issuer of this module (The module pointing to this module)
--module-rules-issuer-layer-not <command...>Logical NOT
--module-rules-layer <command...>Specifies the layer in which the module should be placed in
--module-rules-loader <command...>A loader request
--module-rules-mimetype <command...>Match module mimetype when load from Data URI
--module-rules-mimetype-not <command...>Logical NOT
--module-rules-real-resource <command...>Match the real resource path of the module
--module-rules-real-resource-not <command...>Logical NOT
--module-rules-resource <command...>Match the resource path of the module
--module-rules-resource-not <command...>Logical NOT
--module-rules-resource-fragment <command...>Match the resource fragment of the module
--module-rules-resource-fragment-not <command...>Logical NOT
--module-rules-resource-query <command...>Match the resource query of the module
--module-rules-resource-query-not <command...>Logical NOT
--module-rules-scheme <command...>Match module scheme
--module-rules-scheme-not <command...>Logical NOT
--module-rules-side-effectsFlags a module as with or without side effects
--no-module-rules-side-effectsNegative 'module-rules-side-effects' option
--module-rules-test <command...>Shortcut for resource.test
--module-rules-test-not <command...>Logical NOT
--module-rules-type <command...>Module type to use for the module
--module-rules-use-ident <command...>Unique loader options identifier
--module-rules-use-loader <command...>A loader request
--module-rules-use-options <command...>Options passed to a loader
--module-rules-use <command...>A loader request
--module-rules-resetClear all items provided in 'module.rules' configuration. A list of rules
--module-strict-export-presenceEmit errors instead of warnings when imported names don't exist in imported module. Deprecated: This option has moved to 'module.parser.javascript.strictExportPresence'
--no-module-strict-export-presenceNegative 'module-strict-export-presence' option
--module-strict-this-context-on-importsHandle the this context correctly according to the spec for namespace objects. Deprecated: This option has moved to 'module.parser.javascript.strictThisContextOnImports'
--no-module-strict-this-context-on-importsNegative 'module-strict-this-context-on-imports' option
--module-unknown-context-criticalEnable warnings when using the require function in a not statically analyse-able way. Deprecated: This option has moved to 'module.parser.javascript.unknownContextCritical'
--no-module-unknown-context-criticalNegative 'module-unknown-context-critical' option
--module-unknown-context-recursiveEnable recursive directory lookup when using the require function in a not statically analyse-able way. Deprecated: This option has moved to 'module.parser.javascript.unknownContextRecursive'
--no-module-unknown-context-recursiveNegative 'module-unknown-context-recursive' option
--module-unknown-context-reg-exp [command]Sets the regular expression when using the require function in a not statically analyse-able way. Deprecated: This option has moved to 'module.parser.javascript.unknownContextRegExp'
--no-module-unknown-context-reg-expNegative 'module-unknown-context-reg-exp' option
--module-unknown-context-request <command>Sets the request when using the require function in a not statically analyse-able way. Deprecated: This option has moved to 'module.parser.javascript.unknownContextRequest'
--module-unsafe-cacheCache the resolving of module requests
--no-module-unsafe-cacheNegative 'module-unsafe-cache' option
--module-wrapped-context-criticalEnable warnings for partial dynamic dependencies. Deprecated: This option has moved to 'module.parser.javascript.wrappedContextCritical'
--no-module-wrapped-context-criticalNegative 'module-wrapped-context-critical' option
--module-wrapped-context-recursiveEnable recursive directory lookup for partial dynamic dependencies. Deprecated: This option has moved to 'module.parser.javascript.wrappedContextRecursive'
--no-module-wrapped-context-recursiveNegative 'module-wrapped-context-recursive' option
--module-wrapped-context-reg-exp <command>Set the inner regular expression for partial dynamic dependencies. Deprecated: This option has moved to 'module.parser.javascript.wrappedContextRegExp'
--name <command>Name of the configuration. Used when loading multiple configurations
--no-nodeNegative 'node' option
--node-dirname [command]Include a polyfill for the '__dirname' variable
--no-node-dirnameNegative 'node-dirname' option
--node-filename [command]Include a polyfill for the '__filename' variable
--no-node-filenameNegative 'node-filename' option
--node-global [command]Include a polyfill for the 'global' variable
--no-node-globalNegative 'node-global' option
--optimization-check-wasm-typesCheck for incompatible wasm types when importing/exporting from/to ESM
--no-optimization-check-wasm-typesNegative 'optimization-check-wasm-types' option
--optimization-chunk-ids <command>Define the algorithm to choose chunk ids (named: readable ids for better debugging, deterministic: numeric hash ids for better long term caching, size: numeric ids focused on minimal initial download size, total-size: numeric ids focused on minimal total download size, false: no algorithm used, as custom one can be provided via plugin)
--no-optimization-chunk-idsNegative 'optimization-chunk-ids' option
--optimization-concatenate-modulesConcatenate modules when possible to generate less modules, more efficient code and enable more optimizations by the minimizer
--no-optimization-concatenate-modulesNegative 'optimization-concatenate-modules' option
--optimization-emit-on-errorsEmit assets even when errors occur. Critical errors are emitted into the generated code and will cause errors at runtime
--no-optimization-emit-on-errorsNegative 'optimization-emit-on-errors' option
--optimization-flag-included-chunksAlso flag chunks as loaded which contain a subset of the modules
--no-optimization-flag-included-chunksNegative 'optimization-flag-included-chunks' option
--optimization-inner-graphCreates a module-internal dependency graph for top level symbols, exports and imports, to improve unused exports detection
--no-optimization-inner-graphNegative 'optimization-inner-graph' option
--optimization-mangle-exports [command]Rename exports when possible to generate shorter code (depends on optimization.usedExports and optimization.providedExports, true/"deterministic": generate short deterministic names optimized for caching, "size": generate the shortest possible names)
--no-optimization-mangle-exportsNegative 'optimization-mangle-exports' option
--optimization-mangle-wasm-importsReduce size of WASM by changing imports to shorter strings
--no-optimization-mangle-wasm-importsNegative 'optimization-mangle-wasm-imports' option
--optimization-merge-duplicate-chunksMerge chunks which contain the same modules
--no-optimization-merge-duplicate-chunksNegative 'optimization-merge-duplicate-chunks' option
--optimization-minimizeEnable minimizing the output. Uses optimization.minimizer
--no-optimization-minimizeNegative 'optimization-minimize' option
--optimization-module-ids <command>Define the algorithm to choose module ids (natural: numeric ids in order of usage, named: readable ids for better debugging, hashed: (deprecated) short hashes as ids for better long term caching, deterministic: numeric hash ids for better long term caching, size: numeric ids focused on minimal initial download size, false: no algorithm used, as custom one can be provided via plugin)
--no-optimization-module-idsNegative 'optimization-module-ids' option
--optimization-node-env <command>Set process.env.NODE_ENV to a specific value
--no-optimization-node-envNegative 'optimization-node-env' option
--optimization-portable-recordsGenerate records with relative paths to be able to move the context folder
--no-optimization-portable-recordsNegative 'optimization-portable-records' option
--optimization-provided-exportsFigure out which exports are provided by modules to generate more efficient code
--no-optimization-provided-exportsNegative 'optimization-provided-exports' option
--optimization-real-content-hashUse real [contenthash] based on final content of the assets
--no-optimization-real-content-hashNegative 'optimization-real-content-hash' option
--optimization-remove-available-modulesRemoves modules from chunks when these modules are already included in all parents
--no-optimization-remove-available-modulesNegative 'optimization-remove-available-modules' option
--optimization-remove-empty-chunksRemove chunks which are empty
--no-optimization-remove-empty-chunksNegative 'optimization-remove-empty-chunks' option
--optimization-runtime-chunk [command]Create an additional chunk which contains only the webpack runtime and chunk hash maps
--no-optimization-runtime-chunkNegative 'optimization-runtime-chunk' option
--optimization-runtime-chunk-name <command>The name or name factory for the runtime chunks
--optimization-side-effects [command]Skip over modules which contain no side effects when exports are not used (false: disabled, 'flag': only use manually placed side effects flag, true: also analyse source code for side effects)
--no-optimization-side-effectsNegative 'optimization-side-effects' option
--no-optimization-split-chunksNegative 'optimization-split-chunks' option
--optimization-split-chunks-automatic-name-delimiter <command>Sets the name delimiter for created chunks
--optimization-split-chunks-chunks <command>Select chunks for determining shared modules (defaults to "async", "initial" and "all" requires adding these chunks to the HTML)
--optimization-split-chunks-default-size-types <command...>Size type, like 'javascript', 'webassembly'
--optimization-split-chunks-default-size-types-resetClear all items provided in 'optimization.splitChunks.defaultSizeTypes' configuration. Sets the size types which are used when a number is used for sizes
--optimization-split-chunks-enforce-size-threshold <command>Size of the javascript part of the chunk
Sets the name delimiter for created chunks
--optimization-split-chunks-fallback-cache-group-chunks <command>Select chunks for determining shared modules (defaults to "async", "initial" and "all" requires adding these chunks to the HTML)
--optimization-split-chunks-fallback-cache-group-max-async-size <command>Size of the javascript part of the chunk
--optimization-split-chunks-fallback-cache-group-max-initial-size <command>Size of the javascript part of the chunk
--optimization-split-chunks-fallback-cache-group-max-size <command>Size of the javascript part of the chunk
--optimization-split-chunks-fallback-cache-group-min-size <command>Size of the javascript part of the chunk
--optimization-split-chunks-fallback-cache-group-min-size-reduction <command>Size of the javascript part of the chunk
--optimization-split-chunks-filename <command>Sets the template for the filename for created chunks
--optimization-split-chunks-hide-path-infoPrevents exposing path info when creating names for parts splitted by maxSize
--no-optimization-split-chunks-hide-path-infoNegative 'optimization-split-chunks-hide-path-info' option
--optimization-split-chunks-max-async-requests <command>Maximum number of requests which are accepted for on-demand loading
--optimization-split-chunks-max-async-size <command>Size of the javascript part of the chunk
--optimization-split-chunks-max-initial-requests <command>Maximum number of initial chunks which are accepted for an entry point
--optimization-split-chunks-max-initial-size <command>Size of the javascript part of the chunk
--optimization-split-chunks-max-size <command>Size of the javascript part of the chunk
--optimization-split-chunks-min-chunks <command>Minimum number of times a module has to be duplicated until it's considered for splitting
--optimization-split-chunks-min-remaining-size <command>Size of the javascript part of the chunk
--optimization-split-chunks-min-size <command>Size of the javascript part of the chunk
--optimization-split-chunks-min-size-reduction <command>Size of the javascript part of the chunk
--optimization-split-chunks-name <command>Give chunks created a name (chunks with equal name are merged)
--no-optimization-split-chunks-nameNegative 'optimization-split-chunks-name' option
--optimization-split-chunks-used-exportsCompare used exports when checking common modules. Modules will only be put in the same chunk when exports are equal
--no-optimization-split-chunks-used-exportsNegative 'optimization-split-chunks-used-exports' option
--optimization-used-exports [command]Figure out which exports are used by modules to mangle export names, omit unused exports and generate more efficient code (true: analyse used exports for each runtime, "global": analyse exports globally for all runtimes combined)
--no-optimization-used-exportsNegative 'optimization-used-exports' option
--output-asset-module-filename <command>The filename of asset modules as relative path inside the 'output.path' directory
--output-async-chunksEnable/disable creating async chunks that are loaded on demand
--no-output-async-chunksNegative 'output-async-chunks' option
--output-charsetAdd charset attribute for script tag
--no-output-charsetNegative 'output-charset' option
--output-chunk-filename <command>Specifies the filename template of output files on disk. You must **not** specify an absolute path here, but the path may contain folders separated by '/'! The specified path is joined with the value of the 'output.path' option to determine the location on disk
--output-chunk-format <command>The format of chunks (formats included by default are 'array-push' (web/WebWorker), 'commonjs' (node.js), 'module' (ESM), but others might be added by plugins)
--no-output-chunk-formatNegative 'output-chunk-format' option
--output-chunk-load-timeout <command>Number of milliseconds before chunk request expires
--output-chunk-loading <command>The method of loading chunks (methods included by default are 'jsonp' (web), 'import' (ESM), 'importScripts' (WebWorker), 'require' (sync node.js), 'async-node' (async node.js), but others might be added by plugins)
--no-output-chunk-loadingNegative 'output-chunk-loading' option
--output-chunk-loading-global <command>The global variable used by webpack for loading of chunks
--output-cleanClean the output directory before emit
--no-output-cleanNegative 'output-clean' option
--output-clean-dryLog the assets that should be removed instead of deleting them
--no-output-clean-dryNegative 'output-clean-dry' option
--output-clean-keep <command>Keep these assets
--output-compare-before-emitCheck if to be emitted file already exists and have the same content before writing to output filesystem
--no-output-compare-before-emitNegative 'output-compare-before-emit' option
--output-cross-origin-loading <command>This option enables cross-origin loading of chunks
--no-output-cross-origin-loadingNegative 'output-cross-origin-loading' option
--output-css-chunk-filename <command>Specifies the filename template of output files on disk. You must **not** specify an absolute path here, but the path may contain folders separated by '/'! The specified path is joined with the value of the 'output.path' option to determine the location on disk
--output-css-filename <command>Specifies the filename template of output files on disk. You must **not** specify an absolute path here, but the path may contain folders separated by '/'! The specified path is joined with the value of the 'output.path' option to determine the location on disk
--output-devtool-fallback-module-filename-template <command>Similar to `output.devtoolModuleFilenameTemplate`, but used in the case of duplicate module identifiers
--output-devtool-module-filename-template <command>Filename template string of function for the sources array in a generated SourceMap
--output-devtool-namespace <command>Module namespace to use when interpolating filename template string for the sources array in a generated SourceMap. Defaults to `output.library` if not set. It's useful for avoiding runtime collisions in sourcemaps from multiple webpack projects built as libraries
--output-enabled-chunk-loading-types <command...>The method of loading chunks (methods included by default are 'jsonp' (web), 'import' (ESM), 'importScripts' (WebWorker), 'require' (sync node.js), 'async-node' (async node.js), but others might be added by plugins)
--output-enabled-chunk-loading-types-resetClear all items provided in 'output.enabledChunkLoadingTypes' configuration. List of chunk loading types enabled for use by entry points
--output-enabled-library-types <command...>Type of library (types included by default are 'var', 'module', 'assign', 'assign-properties', 'this', 'window', 'self', 'global', 'commonjs', 'commonjs2', 'commonjs-module', 'commonjs-static', 'amd', 'amd-require', 'umd', 'umd2', 'jsonp', 'system', but others might be added by plugins)
--output-enabled-library-types-resetClear all items provided in 'output.enabledLibraryTypes' configuration. List of library types enabled for use by entry points
--output-enabled-wasm-loading-types <command...>The method of loading WebAssembly Modules (methods included by default are 'fetch' (web/WebWorker), 'async-node' (node.js), but others might be added by plugins)
--output-enabled-wasm-loading-types-resetClear all items provided in 'output.enabledWasmLoadingTypes' configuration. List of wasm loading types enabled for use by entry points
--output-environment-arrow-functionThe environment supports arrow functions ('() => { ... }')
--no-output-environment-arrow-functionNegative 'output-environment-arrow-function' option
--output-environment-big-int-literalThe environment supports BigInt as literal (123n)
--no-output-environment-big-int-literalNegative 'output-environment-big-int-literal' option
--output-environment-constThe environment supports const and let for variable declarations
--no-output-environment-constNegative 'output-environment-const' option
--output-environment-destructuringThe environment supports destructuring ('{ a, b } = obj')
--no-output-environment-destructuringNegative 'output-environment-destructuring' option
--output-environment-dynamic-importThe environment supports an async import() function to import EcmaScript modules
--no-output-environment-dynamic-importNegative 'output-environment-dynamic-import' option
--output-environment-for-ofThe environment supports 'for of' iteration ('for (const x of array) { ... }')
--no-output-environment-for-ofNegative 'output-environment-for-of' option
--output-environment-moduleThe environment supports EcmaScript Module syntax to import EcmaScript modules (import ... from '...')
--no-output-environment-moduleNegative 'output-environment-module' option
--output-environment-optional-chainingThe environment supports optional chaining ('obj?.a' or 'obj?.()')
--no-output-environment-optional-chainingNegative 'output-environment-optional-chaining' option
--output-environment-template-literalThe environment supports template literals
--no-output-environment-template-literalNegative 'output-environment-template-literal' option
--output-filename <command>Specifies the filename template of output files on disk. You must **not** specify an absolute path here, but the path may contain folders separated by '/'! The specified path is joined with the value of the 'output.path' option to determine the location on disk
--output-global-object <command>An expression which is used to address the global object/scope in runtime code
--output-hash-digest <command>Digest type used for the hash
--output-hash-digest-length <command>Number of chars which are used for the hash
--output-hash-function <command>Algorithm used for generation the hash (see node.js crypto package)
--output-hash-salt <command>Any string which is added to the hash to salt it
--output-hot-update-chunk-filename <command>The filename of the Hot Update Chunks. They are inside the output.path directory
--output-hot-update-global <command>The global variable used by webpack for loading of hot update chunks
--output-hot-update-main-filename <command>The filename of the Hot Update Main File. It is inside the 'output.path' directory
--output-iifeWrap javascript code into IIFE's to avoid leaking into global scope
--no-output-iifeNegative 'output-iife' option
--output-import-function-name <command>The name of the native import() function (can be exchanged for a polyfill)
--output-import-meta-name <command>The name of the native import.meta object (can be exchanged for a polyfill)
--output-library <command...>A part of the library name
--output-library-resetClear all items provided in 'output.library' configuration. The name of the library (some types allow unnamed libraries too)
--output-library-amd <command>Name of the exposed AMD library in the UMD
--output-library-commonjs <command>Name of the exposed commonjs export in the UMD
--output-library-root <command...>Part of the name of the property exposed globally by a UMD library
--output-library-root-resetClear all items provided in 'output.library.root' configuration. Name of the property exposed globally by a UMD library
--output-library-auxiliary-comment <command>Append the same comment above each import style
--output-library-auxiliary-comment-amd <command>Set comment for `amd` section in UMD
--output-library-auxiliary-comment-commonjs <command>Set comment for `commonjs` (exports) section in UMD
--output-library-auxiliary-comment-commonjs2 <command>Set comment for `commonjs2` (module.exports) section in UMD
--output-library-auxiliary-comment-root <command>Set comment for `root` (global variable) section in UMD
--output-library-export <command...>Part of the export that should be exposed as library
--output-library-export-resetClear all items provided in 'output.library.export' configuration. Specify which export should be exposed as library
--output-library-name <command...>A part of the library name
--output-library-name-resetClear all items provided in 'output.library.name' configuration. The name of the library (some types allow unnamed libraries too)
--output-library-name-amd <command>Name of the exposed AMD library in the UMD
--output-library-name-commonjs <command>Name of the exposed commonjs export in the UMD
--output-library-name-root <command...>Part of the name of the property exposed globally by a UMD library
--output-library-name-root-resetClear all items provided in 'output.library.name.root' configuration. Name of the property exposed globally by a UMD library
--output-library-type <command>Type of library (types included by default are 'var', 'module', 'assign', 'assign-properties', 'this', 'window', 'self', 'global', 'commonjs', 'commonjs2', 'commonjs-module', 'commonjs-static', 'amd', 'amd-require', 'umd', 'umd2', 'jsonp', 'system', but others might be added by plugins)
--output-library-umd-named-defineIf `output.libraryTarget` is set to umd and `output.library` is set, setting this to true will name the AMD module
--no-output-library-umd-named-defineNegative 'output-library-umd-named-define' option
--output-moduleOutput javascript files as module source type
--no-output-moduleNegative 'output-module' option
--output-path,-o <command>Output location of the file generated by webpack e.g. ./dist/
--output-pathinfo [command]Include comments with information about the modules
--no-output-pathinfoNegative 'output-pathinfo' option
--output-public-path <command>The 'publicPath' specifies the public URL address of the output files when referenced in a browser
--output-script-type <command>This option enables loading async chunks via a custom script type, such as script type="module"
--no-output-script-typeNegative 'output-script-type' option
--output-source-map-filename <command>The filename of the SourceMaps for the JavaScript files. They are inside the 'output.path' directory
--output-source-prefix <command>Prefixes every line of the source in the bundle with this string
--output-strict-module-error-handlingHandles error in module loading correctly at a performance cost. This will handle module error compatible with the EcmaScript Modules spec
--no-output-strict-module-error-handlingNegative 'output-strict-module-error-handling' option
--output-strict-module-exception-handlingHandles exceptions in module loading correctly at a performance cost (Deprecated). This will handle module error compatible with the Node.js CommonJS way
--no-output-strict-module-exception-handlingNegative 'output-strict-module-exception-handling' option
--output-trusted-types [command]Use a Trusted Types policy to create urls for chunks. 'output.uniqueName' is used a default policy name. Passing a string sets a custom policy name. The name of the Trusted Types policy created by webpack to serve bundle chunks
--output-trusted-types-policy-name <command>The name of the Trusted Types policy created by webpack to serve bundle chunks
--output-unique-name <command>A unique name of the webpack build to avoid multiple webpack runtimes to conflict when using globals
--output-wasm-loading <command>The method of loading WebAssembly Modules (methods included by default are 'fetch' (web/WebWorker), 'async-node' (node.js), but others might be added by plugins)
--no-output-wasm-loadingNegative 'output-wasm-loading' option
--output-webassembly-module-filename <command>The filename of WebAssembly modules as relative path inside the 'output.path' directory
--output-worker-chunk-loading <command>The method of loading chunks (methods included by default are 'jsonp' (web), 'import' (ESM), 'importScripts' (WebWorker), 'require' (sync node.js), 'async-node' (async node.js), but others might be added by plugins)
--no-output-worker-chunk-loadingNegative 'output-worker-chunk-loading' option
--output-worker-wasm-loading <command>The method of loading WebAssembly Modules (methods included by default are 'fetch' (web/WebWorker), 'async-node' (node.js), but others might be added by plugins)
--no-output-worker-wasm-loadingNegative 'output-worker-wasm-loading' option
--parallelism <command>The number of parallel processed modules in the compilation
--no-performanceNegative 'performance' option
--performance-hints <command>Sets the format of the hints: warnings, errors or nothing at all
--no-performance-hintsNegative 'performance-hints' option
--performance-max-asset-size <command>File size limit (in bytes) when exceeded, that webpack will provide performance hints
--performance-max-entrypoint-size <command>Total size of an entry point (in bytes)
--profileCapture timing information for each module
--no-profileNegative 'profile' option
--records-input-path <command>Store compiler state to a json file
--no-records-input-pathNegative 'records-input-path' option
--records-output-path <command>Load compiler state from a json file
--no-records-output-pathNegative 'records-output-path' option
--records-path <command>Store/Load compiler state from/to a json file. This will result in persistent ids of modules and chunks. An absolute path is expected. `recordsPath` is used for `recordsInputPath` and `recordsOutputPath` if they left undefined
--no-records-pathNegative 'records-path' option
--resolve-alias-alias <command...>Ignore request (replace with empty module). New request
--no-resolve-alias-aliasNegative 'resolve-alias-alias' option
--resolve-alias-name <command...>Request to be redirected
--resolve-alias-only-moduleRedirect only exact matching request
--no-resolve-alias-only-moduleNegative 'resolve-alias-only-module' option
--resolve-alias-resetClear all items provided in 'resolve.alias' configuration. Redirect module requests
--resolve-alias-fields <command...>Field in the description file (usually package.json) which are used to redirect requests inside the module
--resolve-alias-fields-resetClear all items provided in 'resolve.aliasFields' configuration. Fields in the description file (usually package.json) which are used to redirect requests inside the module
--resolve-cacheEnable caching of successfully resolved requests (cache entries are revalidated)
--no-resolve-cacheNegative 'resolve-cache' option
--resolve-cache-with-contextInclude the context information in the cache identifier when caching
--no-resolve-cache-with-contextNegative 'resolve-cache-with-context' option
--resolve-condition-names <command...>Condition names for exports field entry point
--resolve-condition-names-resetClear all items provided in 'resolve.conditionNames' configuration. Condition names for exports field entry point
--resolve-description-files <command...>Filename used to find a description file (like a package.json)
--resolve-description-files-resetClear all items provided in 'resolve.descriptionFiles' configuration. Filenames used to find a description file (like a package.json)
--resolve-enforce-extensionEnforce the resolver to use one of the extensions from the extensions option (User must specify requests without extension)
--no-resolve-enforce-extensionNegative 'resolve-enforce-extension' option
--resolve-exports-fields <command...>Field name from the description file (usually package.json) which is used to provide entry points of a package
--resolve-exports-fields-resetClear all items provided in 'resolve.exportsFields' configuration. Field names from the description file (usually package.json) which are used to provide entry points of a package
--resolve-extensions <command...>Extension added to the request when trying to find the file
--resolve-extensions-resetClear all items provided in 'resolve.extensions' configuration. Extensions added to the request when trying to find the file
--resolve-fallback-alias <command...>Ignore request (replace with empty module). New request
--no-resolve-fallback-aliasNegative 'resolve-fallback-alias' option
--resolve-fallback-name <command...>Request to be redirected
--resolve-fallback-only-moduleRedirect only exact matching request
--no-resolve-fallback-only-moduleNegative 'resolve-fallback-only-module' option
--resolve-fallback-resetClear all items provided in 'resolve.fallback' configuration. Redirect module requests
--resolve-fully-specifiedTreats the request specified by the user as fully specified, meaning no extensions are added and the mainFiles in directories are not resolved (This doesn't affect requests from mainFields, aliasFields or aliases)
--no-resolve-fully-specifiedNegative 'resolve-fully-specified' option
--resolve-imports-fields <command...>Field name from the description file (usually package.json) which is used to provide internal request of a package (requests starting with # are considered as internal)
--resolve-imports-fields-resetClear all items provided in 'resolve.importsFields' configuration. Field names from the description file (usually package.json) which are used to provide internal request of a package (requests starting with # are considered as internal)
--resolve-main-fields <command...>Field name from the description file (package.json) which are used to find the default entry point
--resolve-main-fields-resetClear all items provided in 'resolve.mainFields' configuration. Field names from the description file (package.json) which are used to find the default entry point
--resolve-main-files <command...>Filename used to find the default entry point if there is no description file or main field
--resolve-main-files-resetClear all items provided in 'resolve.mainFiles' configuration. Filenames used to find the default entry point if there is no description file or main field
--resolve-modules <command...>Folder name or directory path where to find modules
--resolve-modules-resetClear all items provided in 'resolve.modules' configuration. Folder names or directory paths where to find modules
--resolve-prefer-absolutePrefer to resolve server-relative URLs (starting with '/') as absolute paths before falling back to resolve in 'resolve.roots'
--no-resolve-prefer-absoluteNegative 'resolve-prefer-absolute' option
--resolve-prefer-relativePrefer to resolve module requests as relative request and fallback to resolving as module
--no-resolve-prefer-relativeNegative 'resolve-prefer-relative' option
--resolve-restrictions <command...>Resolve restriction. Resolve result must fulfill this restriction
--resolve-restrictions-resetClear all items provided in 'resolve.restrictions' configuration. A list of resolve restrictions. Resolve results must fulfill all of these restrictions to resolve successfully. Other resolve paths are taken when restrictions are not met
--resolve-roots <command...>Directory in which requests that are server-relative URLs (starting with '/') are resolved
--resolve-roots-resetClear all items provided in 'resolve.roots' configuration. A list of directories in which requests that are server-relative URLs (starting with '/') are resolved
--resolve-symlinksEnable resolving symlinks to the original location
--no-resolve-symlinksNegative 'resolve-symlinks' option
--resolve-unsafe-cacheEnable caching of successfully resolved requests (cache entries are not revalidated)
--no-resolve-unsafe-cacheNegative 'resolve-unsafe-cache' option
--resolve-use-sync-file-system-callsUse synchronous filesystem calls for the resolver
--no-resolve-use-sync-file-system-callsNegative 'resolve-use-sync-file-system-calls' option
--resolve-loader-alias-alias <command...>Ignore request (replace with empty module). New request
--no-resolve-loader-alias-aliasNegative 'resolve-loader-alias-alias' option
--resolve-loader-alias-name <command...>Request to be redirected
--resolve-loader-alias-only-moduleRedirect only exact matching request
--no-resolve-loader-alias-only-moduleNegative 'resolve-loader-alias-only-module' option
--resolve-loader-alias-resetClear all items provided in 'resolveLoader.alias' configuration. Redirect module requests
--resolve-loader-alias-fields <command...>Field in the description file (usually package.json) which are used to redirect requests inside the module
--resolve-loader-alias-fields-resetClear all items provided in 'resolveLoader.aliasFields' configuration. Fields in the description file (usually package.json) which are used to redirect requests inside the module
--resolve-loader-cacheEnable caching of successfully resolved requests (cache entries are revalidated)
--no-resolve-loader-cacheNegative 'resolve-loader-cache' option
--resolve-loader-cache-with-contextInclude the context information in the cache identifier when caching
--no-resolve-loader-cache-with-contextNegative 'resolve-loader-cache-with-context' option
--resolve-loader-condition-names <command...>Condition names for exports field entry point
--resolve-loader-condition-names-resetClear all items provided in 'resolveLoader.conditionNames' configuration. Condition names for exports field entry point
--resolve-loader-description-files <command...>Filename used to find a description file (like a package.json)
--resolve-loader-description-files-resetClear all items provided in 'resolveLoader.descriptionFiles' configuration. Filenames used to find a description file (like a package.json)
--resolve-loader-enforce-extensionEnforce the resolver to use one of the extensions from the extensions option (User must specify requests without extension)
--no-resolve-loader-enforce-extensionNegative 'resolve-loader-enforce-extension' option
--resolve-loader-exports-fields <command...>Field name from the description file (usually package.json) which is used to provide entry points of a package
--resolve-loader-exports-fields-resetClear all items provided in 'resolveLoader.exportsFields' configuration. Field names from the description file (usually package.json) which are used to provide entry points of a package
--resolve-loader-extensions <command...>Extension added to the request when trying to find the file
--resolve-loader-extensions-resetClear all items provided in 'resolveLoader.extensions' configuration. Extensions added to the request when trying to find the file
--resolve-loader-fallback-alias <command...>Ignore request (replace with empty module). New request
--no-resolve-loader-fallback-aliasNegative 'resolve-loader-fallback-alias' option
--resolve-loader-fallback-name <command...>Request to be redirected
--resolve-loader-fallback-only-moduleRedirect only exact matching request
--no-resolve-loader-fallback-only-moduleNegative 'resolve-loader-fallback-only-module' option
--resolve-loader-fallback-resetClear all items provided in 'resolveLoader.fallback' configuration. Redirect module requests
--resolve-loader-fully-specifiedTreats the request specified by the user as fully specified, meaning no extensions are added and the mainFiles in directories are not resolved (This doesn't affect requests from mainFields, aliasFields or aliases)
--no-resolve-loader-fully-specifiedNegative 'resolve-loader-fully-specified' option
--resolve-loader-imports-fields <command...>Field name from the description file (usually package.json) which is used to provide internal request of a package (requests starting with # are considered as internal)
--resolve-loader-imports-fields-resetClear all items provided in 'resolveLoader.importsFields' configuration. Field names from the description file (usually package.json) which are used to provide internal request of a package (requests starting with # are considered as internal)
--resolve-loader-main-fields <command...>Field name from the description file (package.json) which are used to find the default entry point
--resolve-loader-main-fields-resetClear all items provided in 'resolveLoader.mainFields' configuration. Field names from the description file (package.json) which are used to find the default entry point
--resolve-loader-main-files <command...>Filename used to find the default entry point if there is no description file or main field
--resolve-loader-main-files-resetClear all items provided in 'resolveLoader.mainFiles' configuration. Filenames used to find the default entry point if there is no description file or main field
--resolve-loader-modules <command...>Folder name or directory path where to find modules
--resolve-loader-modules-resetClear all items provided in 'resolveLoader.modules' configuration. Folder names or directory paths where to find modules
--resolve-loader-prefer-absolutePrefer to resolve server-relative URLs (starting with '/') as absolute paths before falling back to resolve in 'resolve.roots'
--no-resolve-loader-prefer-absoluteNegative 'resolve-loader-prefer-absolute' option
--resolve-loader-prefer-relativePrefer to resolve module requests as relative request and fallback to resolving as module
--no-resolve-loader-prefer-relativeNegative 'resolve-loader-prefer-relative' option
--resolve-loader-restrictions <command...>Resolve restriction. Resolve result must fulfill this restriction
--resolve-loader-restrictions-resetClear all items provided in 'resolveLoader.restrictions' configuration. A list of resolve restrictions. Resolve results must fulfill all of these restrictions to resolve successfully. Other resolve paths are taken when restrictions are not met
--resolve-loader-roots <command...>Directory in which requests that are server-relative URLs (starting with '/') are resolved
--resolve-loader-roots-resetClear all items provided in 'resolveLoader.roots' configuration. A list of directories in which requests that are server-relative URLs (starting with '/') are resolved
--resolve-loader-symlinksEnable resolving symlinks to the original location
--no-resolve-loader-symlinksNegative 'resolve-loader-symlinks' option
--resolve-loader-unsafe-cacheEnable caching of successfully resolved requests (cache entries are not revalidated)
--no-resolve-loader-unsafe-cacheNegative 'resolve-loader-unsafe-cache' option
--resolve-loader-use-sync-file-system-callsUse synchronous filesystem calls for the resolver
--no-resolve-loader-use-sync-file-system-callsNegative 'resolve-loader-use-sync-file-system-calls' option
--snapshot-build-dependencies-hashUse hashes of the content of the files/directories to determine invalidation
--no-snapshot-build-dependencies-hashNegative 'snapshot-build-dependencies-hash' option
--snapshot-build-dependencies-timestampUse timestamps of the files/directories to determine invalidation
--no-snapshot-build-dependencies-timestampNegative 'snapshot-build-dependencies-timestamp' option
--snapshot-immutable-paths <command...>A RegExp matching an immutable directory (usually a package manager cache directory, including the tailing slash) A path to an immutable directory (usually a package manager cache directory)
--snapshot-immutable-paths-resetClear all items provided in 'snapshot.immutablePaths' configuration. List of paths that are managed by a package manager and contain a version or hash in its path so all files are immutable
--snapshot-managed-paths <command...>A RegExp matching a managed directory (usually a node_modules directory, including the tailing slash) A path to a managed directory (usually a node_modules directory)
--snapshot-managed-paths-resetClear all items provided in 'snapshot.managedPaths' configuration. List of paths that are managed by a package manager and can be trusted to not be modified otherwise
--snapshot-module-hashUse hashes of the content of the files/directories to determine invalidation
--no-snapshot-module-hashNegative 'snapshot-module-hash' option
--snapshot-module-timestampUse timestamps of the files/directories to determine invalidation
--no-snapshot-module-timestampNegative 'snapshot-module-timestamp' option
--snapshot-resolve-hashUse hashes of the content of the files/directories to determine invalidation
--no-snapshot-resolve-hashNegative 'snapshot-resolve-hash' option
--snapshot-resolve-timestampUse timestamps of the files/directories to determine invalidation
--no-snapshot-resolve-timestampNegative 'snapshot-resolve-timestamp' option
--snapshot-resolve-build-dependencies-hashUse hashes of the content of the files/directories to determine invalidation
--no-snapshot-resolve-build-dependencies-hashNegative 'snapshot-resolve-build-dependencies-hash' option
--snapshot-resolve-build-dependencies-timestampUse timestamps of the files/directories to determine invalidation
--no-snapshot-resolve-build-dependencies-timestampNegative 'snapshot-resolve-build-dependencies-timestamp' option
--stats [command]It instructs webpack on how to treat the stats e.g. verbose
--no-statsDisable stats output
--stats-allFallback value for stats options when an option is not defined (has precedence over local webpack defaults)
--no-stats-allNegative 'stats-all' option
--stats-assetsAdd assets information
--no-stats-assetsNegative 'stats-assets' option
--stats-assets-sort <command>Sort the assets by that field
--stats-assets-space <command>Space to display assets (groups will be collapsed to fit this space)
--stats-built-atAdd built at time information
--no-stats-built-atNegative 'stats-built-at' option
--stats-cachedAdd information about cached (not built) modules (deprecated: use 'cachedModules' instead)
--no-stats-cachedNegative 'stats-cached' option
--stats-cached-assetsShow cached assets (setting this to `false` only shows emitted files)
--no-stats-cached-assetsNegative 'stats-cached-assets' option
--stats-cached-modulesAdd information about cached (not built) modules
--no-stats-cached-modulesNegative 'stats-cached-modules' option
--stats-childrenAdd children information
--no-stats-childrenNegative 'stats-children' option
--stats-chunk-group-auxiliaryDisplay auxiliary assets in chunk groups
--no-stats-chunk-group-auxiliaryNegative 'stats-chunk-group-auxiliary' option
--stats-chunk-group-childrenDisplay children of chunk groups
--no-stats-chunk-group-childrenNegative 'stats-chunk-group-children' option
--stats-chunk-group-max-assets <command>Limit of assets displayed in chunk groups
--stats-chunk-groupsDisplay all chunk groups with the corresponding bundles
--no-stats-chunk-groupsNegative 'stats-chunk-groups' option
--stats-chunk-modulesAdd built modules information to chunk information
--no-stats-chunk-modulesNegative 'stats-chunk-modules' option
--stats-chunk-modules-space <command>Space to display chunk modules (groups will be collapsed to fit this space, value is in number of modules/group)
--stats-chunk-originsAdd the origins of chunks and chunk merging info
--no-stats-chunk-originsNegative 'stats-chunk-origins' option
--stats-chunk-relationsAdd information about parent, children and sibling chunks to chunk information
--no-stats-chunk-relationsNegative 'stats-chunk-relations' option
--stats-chunksAdd chunk information
--no-stats-chunksNegative 'stats-chunks' option
--stats-chunks-sort <command>Sort the chunks by that field
--stats-colorsEnables/Disables colorful output
--no-stats-colorsNegative 'stats-colors' option
--stats-colors-bold <command>Custom color for bold text
--stats-colors-cyan <command>Custom color for cyan text
--stats-colors-green <command>Custom color for green text
--stats-colors-magenta <command>Custom color for magenta text
--stats-colors-red <command>Custom color for red text
--stats-colors-yellow <command>Custom color for yellow text
--stats-context <command>Context directory for request shortening
--stats-dependent-modulesShow chunk modules that are dependencies of other modules of the chunk
--no-stats-dependent-modulesNegative 'stats-dependent-modules' option
--stats-depthAdd module depth in module graph
--no-stats-depthNegative 'stats-depth' option
--stats-entrypoints [command]Display the entry points with the corresponding bundles
--no-stats-entrypointsNegative 'stats-entrypoints' option
--stats-envAdd --env information
--no-stats-envNegative 'stats-env' option
--stats-error-details [command]Add details to errors (like resolving log)
--no-stats-error-detailsNegative 'stats-error-details' option
--stats-error-stackAdd internal stack trace to errors
--no-stats-error-stackNegative 'stats-error-stack' option
--stats-errorsAdd errors
--no-stats-errorsNegative 'stats-errors' option
--stats-errors-countAdd errors count
--no-stats-errors-countNegative 'stats-errors-count' option
--stats-exclude-assets <command...>Suppress assets that match the specified filters. Filters can be Strings, RegExps or Functions
--stats-exclude-assets-resetClear all items provided in 'stats.excludeAssets' configuration. Suppress assets that match the specified filters. Filters can be Strings, RegExps or Functions
--stats-exclude-modules [command...]Suppress modules that match the specified filters. Filters can be Strings, RegExps, Booleans or Functions
--no-stats-exclude-modulesNegative 'stats-exclude-modules' option
--stats-exclude-modules-resetClear all items provided in 'stats.excludeModules' configuration. Suppress modules that match the specified filters. Filters can be Strings, RegExps, Booleans or Functions
--stats-group-assets-by-chunkGroup assets by how their are related to chunks
--no-stats-group-assets-by-chunkNegative 'stats-group-assets-by-chunk' option
--stats-group-assets-by-emit-statusGroup assets by their status (emitted, compared for emit or cached)
--no-stats-group-assets-by-emit-statusNegative 'stats-group-assets-by-emit-status' option
--stats-group-assets-by-extensionGroup assets by their extension
--no-stats-group-assets-by-extensionNegative 'stats-group-assets-by-extension' option
--stats-group-assets-by-infoGroup assets by their asset info (immutable, development, hotModuleReplacement, etc)
--no-stats-group-assets-by-infoNegative 'stats-group-assets-by-info' option
--stats-group-assets-by-pathGroup assets by their path
--no-stats-group-assets-by-pathNegative 'stats-group-assets-by-path' option
--stats-group-modules-by-attributesGroup modules by their attributes (errors, warnings, assets, optional, orphan, or dependent)
--no-stats-group-modules-by-attributesNegative 'stats-group-modules-by-attributes' option
--stats-group-modules-by-cache-statusGroup modules by their status (cached or built and cacheable)
--no-stats-group-modules-by-cache-statusNegative 'stats-group-modules-by-cache-status' option
--stats-group-modules-by-extensionGroup modules by their extension
--no-stats-group-modules-by-extensionNegative 'stats-group-modules-by-extension' option
--stats-group-modules-by-layerGroup modules by their layer
--no-stats-group-modules-by-layerNegative 'stats-group-modules-by-layer' option
--stats-group-modules-by-pathGroup modules by their path
--no-stats-group-modules-by-pathNegative 'stats-group-modules-by-path' option
--stats-group-modules-by-typeGroup modules by their type
--no-stats-group-modules-by-typeNegative 'stats-group-modules-by-type' option
--stats-group-reasons-by-originGroup reasons by their origin module
--no-stats-group-reasons-by-originNegative 'stats-group-reasons-by-origin' option
--stats-hashAdd the hash of the compilation
--no-stats-hashNegative 'stats-hash' option
--stats-idsAdd ids
--no-stats-idsNegative 'stats-ids' option
--stats-logging [command]Specify log level of logging output. Enable/disable logging output (`true`: shows normal logging output, loglevel: log)
--no-stats-loggingNegative 'stats-logging' option
--stats-logging-debug [command...]Enable/Disable debug logging for all loggers. Include debug logging of specified loggers (i. e. for plugins or loaders). Filters can be Strings, RegExps or Functions
--no-stats-logging-debugNegative 'stats-logging-debug' option
--stats-logging-debug-resetClear all items provided in 'stats.loggingDebug' configuration. Include debug logging of specified loggers (i. e. for plugins or loaders). Filters can be Strings, RegExps or Functions
--stats-logging-traceAdd stack traces to logging output
--no-stats-logging-traceNegative 'stats-logging-trace' option
--stats-module-assetsAdd information about assets inside modules
--no-stats-module-assetsNegative 'stats-module-assets' option
--stats-module-traceAdd dependencies and origin of warnings/errors
--no-stats-module-traceNegative 'stats-module-trace' option
--stats-modulesAdd built modules information
--no-stats-modulesNegative 'stats-modules' option
--stats-modules-sort <command>Sort the modules by that field
--stats-modules-space <command>Space to display modules (groups will be collapsed to fit this space, value is in number of modules/groups)
--stats-nested-modulesAdd information about modules nested in other modules (like with module concatenation)
--no-stats-nested-modulesNegative 'stats-nested-modules' option
--stats-nested-modules-space <command>Space to display modules nested within other modules (groups will be collapsed to fit this space, value is in number of modules/group)
--stats-optimization-bailoutShow reasons why optimization bailed out for modules
--no-stats-optimization-bailoutNegative 'stats-optimization-bailout' option
--stats-orphan-modulesAdd information about orphan modules
--no-stats-orphan-modulesNegative 'stats-orphan-modules' option
--stats-output-pathAdd output path information
--no-stats-output-pathNegative 'stats-output-path' option
--stats-performanceAdd performance hint flags
--no-stats-performanceNegative 'stats-performance' option
--stats-preset [command]Preset for the default values
--no-stats-presetNegative 'stats-preset' option
--stats-provided-exportsShow exports provided by modules
--no-stats-provided-exportsNegative 'stats-provided-exports' option
--stats-public-pathAdd public path information
--no-stats-public-pathNegative 'stats-public-path' option
--stats-reasonsAdd information about the reasons why modules are included
--no-stats-reasonsNegative 'stats-reasons' option
--stats-reasons-space <command>Space to display reasons (groups will be collapsed to fit this space)
--stats-related-assetsAdd information about assets that are related to other assets (like SourceMaps for assets)
--no-stats-related-assetsNegative 'stats-related-assets' option
--stats-runtimeAdd information about runtime modules (deprecated: use 'runtimeModules' instead)
--no-stats-runtimeNegative 'stats-runtime' option
--stats-runtime-modulesAdd information about runtime modules
--no-stats-runtime-modulesNegative 'stats-runtime-modules' option
--stats-sourceAdd the source code of modules
--no-stats-sourceNegative 'stats-source' option
--stats-timingsAdd timing information
--no-stats-timingsNegative 'stats-timings' option
--stats-used-exportsShow exports used by modules
--no-stats-used-exportsNegative 'stats-used-exports' option
--stats-versionAdd webpack version information
--no-stats-versionNegative 'stats-version' option
--stats-warningsAdd warnings
--no-stats-warningsNegative 'stats-warnings' option
--stats-warnings-countAdd warnings count
--no-stats-warnings-countNegative 'stats-warnings-count' option
--stats-warnings-filter <command...>Suppress listing warnings that match the specified filters (they will still be counted). Filters can be Strings, RegExps or Functions
--stats-warnings-filter-resetClear all items provided in 'stats.warningsFilter' configuration. Suppress listing warnings that match the specified filters (they will still be counted). Filters can be Strings, RegExps or Functions
--target,-t <command...>Sets the build target e.g. node
--no-targetNegative 'target' option
--target-resetClear all items provided in 'target' configuration. Environment to build for. An array of environments to build for all of them when possible
--watch,-wWatch for files changes
--no-watchDo not watch for file changes
--watch-options-aggregate-timeout <command>Delay the rebuilt after the first change. Value is a time in ms
--watch-options-follow-symlinksResolve symlinks and watch symlink and real file. This is usually not needed as webpack already resolves symlinks ('resolve.symlinks')
--no-watch-options-follow-symlinksNegative 'watch-options-follow-symlinks' option
--watch-options-ignored <command...>A glob pattern for files that should be ignored from watching. Ignore some files from watching (glob pattern or regexp)
--watch-options-ignored-resetClear all items provided in 'watchOptions.ignored' configuration. Ignore some files from watching (glob pattern or regexp)
--watch-options-poll [command]`number`: use polling with specified interval. `true`: use polling
--no-watch-options-pollNegative 'watch-options-poll' option
--watch-options-stdinStop watching when stdin stream has ended
--no-watch-options-stdinDo not stop watching when stdin stream has ended