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 methods available in code compiled with Rspack. When using Rspack to bundle your application, you can pick from a variety of module syntax styles including ES6, CommonJS.
While Rspack supports multiple module syntaxes, we recommend following a single syntax for consistency and to avoid odd behaviors/bugs.
Actually Rspack would enforce the recommendation for .mjs
files, .cjs
files or .js
files when their nearest parent package.json
file contains a "type"
field with a value of either "module"
or "commonjs"
. Please pay attention to these enforcements before you read on
.mjs
or .js
with "type": "module"
in package.json
require
, module.exports
or exports
.cjs
or .js
with "type": "commonjs" in package.json
Rspack support ES6 module syntax natively, you can use static import
, export
and import()
syntax.
Keep in mind that you will still probably need SWC or Babel for other ES6+ features.
Statically import
the export
s of another module.
You can also import
Data URI
Export anything as a default
or named export.
Dynamically load modules. Calls to import()
are treated as split points, meaning the requested module and its children are split out into a separate chunk.
This feature relies on Promise
internally. If you use import() with older browsers, remember to shim Promise
using a polyfill such as es6-promise or promise-polyfill.
It is not possible to use a fully dynamic import statement, such as import(foo)
. Because foo
could potentially be any path to any file in your system or project.
The import()
must contain at least some information about where the module is located. Bundling can be limited to a specific directory or set of files so that when you are using a dynamic expression - every module that could potentially be requested on an import()
call is included. For example, import(
./locale/${language}.json)
will cause every .json
file in the ./locale
directory to be bundled into the new chunk. At run time, when the variable language
has been computed, any file like english.json
or german.json
will be available for consumption.
Inline comments to make features work. By adding comments to the import, we can do things such as name our chunk or select different modes. For a full list of these magic comments see the code below followed by an explanation of what these comments do.
boolean
Disables dynamic import parsing when set to true.
Note that setting webpackIgnore to true opts out of code splitting.
"eager" | "lazy" | "weak" | "lazy-once"
Different modes for resolving dynamic imports can be specified. The following options are supported
'lazy'
(default): Generates a lazy-loadable chunk for each import()
ed module.'lazy-once'
: Generates a single lazy-loadable chunk that can satisfy all calls to import()
. The chunk will be fetched on the first call to import()
, and subsequent calls to import()
will use the same network response. Note that this only makes sense in the case of a partially dynamic statement, e.g. import("./locales/${language}.json")
, where multiple module paths that can potentially be requested.'eager'
: Generates no extra chunk. All modules are included in the current chunk and no additional network requests are made. A Promise is still returned but is already resolved. In contrast to a static import, the module isn't executed until the call to import()
is made.'weak'
: Tries to load the module if the module function has already been loaded in some other way (e.g. another chunk imported it or a script containing the module was loaded). A Promise is still returned, but only successfully resolves if the chunks are already on the client. If the module is not available, the Promise is rejected. A network request will never be performed. This is useful for universal rendering when required chunks are always manually served in initial requests (embedded within the page), but not in cases where app navigation will trigger an import not initially served.number
: chunk prefetch priorityboolean
: false
means not to prefetch, true
means priority is 0
Tells the browser that the resource is probably needed for some navigation in the future, see Prefetching/Preloading modules for more details.
number
: chunk preload priorityboolean
: false
means not to preload, true
means priority is 0
Tells the browser that the resource might be needed during the current navigation, , see Prefetching/Preloading modules for more details.
string
A name for the new chunk.
"low" | "high" | "auto"
Set fetchPriority
for specific dynamic imports. It's also possible to set a global default value for all dynamic imports by using the module.parser.javascript.dynamicImportFetchPriority
option.
Regexp
A regular expression that will be matched against during import resolution. Only modules that match will be bundled.
Regexp
A regular expression that will be matched against during import resolution. Any module that matches will not be bundled.
Note that webpackInclude
and webpackExclude
options do not interfere with the prefix. eg: ./locale
.
string | string[]
動的にimport()
されたモジュールの指定されたエクスポートのみをバンドルするようにwebpackに指示します。これにより、チャンクの出力サイズを削減できます。
RspackはCommonJS
構文もネイティブにサポートしています。require
とmodule.exports
メソッドを使用できます。
別のモジュールからエクスポートを同期的に取得します。
モジュールのIDを同期的に取得します。require.cache[id]
または__webpack_require__(id)
(このような使用方法を避けるのが最適です)でのみ使用できる不透明な値として扱うことをお勧めします。
モジュールIDの型は、optimization.moduleIds
設定に応じて数値または文字列になります。
同じモジュールを複数回requireしても、モジュールの実行は1回のみ、エクスポートも1回のみです。そのため、ランタイムにキャッシュが存在します。このキャッシュから値を削除すると、モジュールが新しく実行され、新しいエクスポートが生成されます。
require.context
は、モジュールのセットを動的にrequireできるwebpack固有の関数です。
コードでrequire.context
を使用でき、Rspackはビルドプロセス中に一致するモジュールを解析して参照します。
require.context
の戻り値は、import.meta.webpackContextと同じです。より強力なimport.meta.webpackContext
の使用をお勧めします。
Rspackは静的解析を使用して、コンパイル中にrequire.context
のパラメータを解析します。そのため、パラメータはリテラルでなければなりません。
たとえば、filter
の値は変数にすることはできませんし、new RegExp()
によって生成された値にすることもできません。正規表現リテラルのみが可能です。
require.ensure()
はrspack/webpack特有のものであり、import()
によって置き換えられました。
指定されたdependencies
を非同期にロードされる個別のバンドルに分割します。CommonJSモジュール構文を使用する場合、これはdependencies
を動的にロードする唯一の方法です。つまり、このコードは実行時に実行でき、特定の条件が満たされた場合にのみ依存関係をロードします。
この機能は内部的にPromiseに依存しています。古いブラウザでrequire.ensure
を使用する場合は、es6-promiseまたはpromise-polyfillなどのポリフィルを使用してPromiseをshimすることを忘れないでください。
Rspackは、import
構文とrequire
構文を使用してData URIモジュールのインポートをサポートしています。
import
require
さらに、Base64でエンコードされたリクエストもサポートされています。
Data URIモジュールは、Loaderと組み合わせて実行時にカスタムモジュールを動的にロードするなど、仮想モジュールを実装する方法として使用できます。