The content of this section is derived from the content of the following links and is subject to the CC BY 4.0 license.
The following contents can be assumed to be the result of modifications and deletions based on the original contents if not specifically stated.
This plugin enables more fine grained control of source map generation. It is also enabled automatically by certain settings of the devtool configuration option.
string RegExp [string, RegExp]Include source maps for modules based on their extension (defaults to .js, .mjs, and .css).
string RegExp [string, RegExp]Include source maps for module paths that match the given value.
string RegExp [string, RegExp]Exclude modules that match the given value from source map generation.
Defines the output filename of the SourceMap (will be inlined if no value is provided).
string functionAppends the given value to the original asset. Usually the #sourceMappingURL comment. [url] is replaced with a URL to the source map file. Path parameters are supported: [chunk], [filename] and [contenthash]. Setting append to false disables the appending.
stringSee output.devtoolModuleFilenameTemplate.
stringSee link above.
stringbooleantrueIndicates whether loaders should generate source maps.
booleantrueIndicates whether column mappings should be used.
booleanfalsePrevents the source file content from being included in the source map.
stringEmits absolute URLs with public path prefix, e.g. https://example.com/project/.
stringMakes the [file] argument relative to this directory.
The fileContext option is useful when you want to store source maps in an upper level directory to avoid ../../ appearing in the absolute [url].
stringProvide a custom value for the sourceRoot property in the SourceMap.
Setting module and/or columns to false will yield less accurate source maps but will also improve compilation performance significantly.
If you want to use a custom configuration for this plugin in development mode, make sure to disable the default one. I.e. set devtool: false.
The following examples demonstrate some common use cases for this plugin.
You can use the following code to replace the configuration option devtool: inline-source-map with an equivalent custom plugin configuration:
The following code would exclude source maps for any modules in the vendor.js bundle:
Set a URL for source maps. Useful for hosting them on a host that requires authorization.
And for cases when source maps are stored in the upper level directory:
With the following config:
Will produce the following URL: