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 section covers all variables available in code compiled with webpack. Modules will have access to certain data from the compilation process through module
and other variables.
Indicates whether or not Hot Module Replacement is enabled and provides an interface to the process. See the HMR API page for details.
import.meta.webpackContext
is a function specific to webpack that allows you to dynamically import a set of modules.
You can use import.meta.webpackContext
in your code, and Rspack will parse and reference the matching modules during the build process.
The return value of import.meta.webpackContext
is the same as import.meta.webpackContext. We recommend using import.meta.webpackContext
, which is more powerful.
The first arguments passed to
import.meta.webpackContext()
must be literals.
The context returned by import.meta.webpackContext()
is a function that takes a request
argument (module path).
This function has three properties: resolve
, keys
, and id
.
resolve
is a function and returns the module id of the parsed request.keys
is a function that returns an array of all possible requests that the context module can handle.id
is the module id of the context module. This may be useful for module.hot.accept
.This can be useful if you want to require all files in a directory or matching a pattern.
Consider a scenario where you have a folder structure like this:
You can use import.meta.webpackContext()
to dynamically import all component files in the folder:
import.meta.webpackContext()
streamlines the process of module importation especially when you have a lot of files to manage. When using it, please avoid matching unnecessary files, as this might lead to significantly increased build time and output size.
An alias for module.hot
, however import.meta.webpackHot
can be used in strict ESM while module.hot
can't.
Depending on the configuration option node.__dirname
:
false
: Not definedmock
: equal to '/'
true
: node.js __dirnameIf used inside an expression that is parsed by the Parser, the configuration option is treated as true
.
The resource query of the current module. If the following require
call was made, then the query string would be available in file.js
.
Access to the internal object of all modules.
It provides access to the hash of the compilation.
Equals the configuration option's output.publicPath
.
Access to name of current chunk.
Access the runtime id of current entry.