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.
The devtool
configuration is used to control the behavior of the Source Map generation.
eval
The main types of Source Map generated behaviors are source-map
, eval
, cheap
, module
, inline
, nosources
and hidden
, and they can be combined.
source-map
is the most basic behavior, indicating the generation of Source Map, which has a partial overhead on build performance when Source Map is turned on.
eval
wraps the module generated code with eval()
, so Rspack can internally cache the module generated results, so when eval
is used in combination with source-map
, it optimizes the speed of Source Map generation when rebuilding.
cheap
means that the Source Map will only generate the mapping of rows, ignoring the mapping of columns, in order to speed up the generation of the Source Map.
module
is used to control whether the loader needs to return the Source Map, so without module
, the Source Map can only map code that will be processed by the loader, and because the loader does not need to process the Source Map, the Source Map generation speed will be improved.
inline
indicates whether the generated Source Map is inlined into the end of the file via the data url.
nosources
is used to control whether the generated Source Map contains source code content to reduce the size of the generated Source Map.
hidden
is used to control whether the end of the generated file contains the # sourceMappingURL=...
annotation. The browser developer tools and VS Code etc. will look for the Source Map by the path or data url of this annotation in order to map the product's row number back to its location in the source code during debugging.