Skip to content

Update module-methods.mdx #7633

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update module-methods.mdx #7633

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f526fbf
Update module-methods.mdx
adriancuadrado Jun 6, 2025
f413041
Update module-methods.mdx
adriancuadrado Jun 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions src/content/api/module-methods.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,7 +97,8 @@ W> This feature relies on [`Promise`](https://developer.mozilla.org/en-US/docs/W

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.
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 only bundle all `.json` files in the `./locale` directory and subdirectories into the new chunk and exclude files with other file extensions. At run time, when the variable `language` has been computed, any file like `english.json` or `german.json` will be available for consumption.

```javascript
// imagine we had a method to get language from cookies or other storage
Expand All @@ -111,7 +112,7 @@ T> Using the [`webpackInclude` and `webpackExclude`](/api/module-methods/#magic-

#### Magic Comments

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.
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.

```js
// Single target
Expand All @@ -137,6 +138,8 @@ import(
import(/* webpackIgnore: true */ 'ignored-module.js');
```

T> Single line comments (`//`) are also supported. JSDoc comments (`/** */`) are not.

##### webpackIgnore

**JavaScript Usage**
Expand Down
Loading