Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 014d483

Browse filesBrowse files
aduh95targos
authored andcommitted
doc: clarify entry point behavior when using loader hooks
Fixes: #41275 PR-URL: #41304 Reviewed-By: Guy Bedford <guybedford@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
1 parent 1d75436 commit 014d483
Copy full SHA for 014d483

File tree

Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed
Open diff view settings
Collapse file

‎doc/api/esm.md‎

Copy file name to clipboardExpand all lines: doc/api/esm.md
+2-2Lines changed: 2 additions & 2 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -628,8 +628,8 @@ node b.mjs # works
628628
To customize the default module resolution, loader hooks can optionally be
629629
provided via a `--experimental-loader ./loader-name.mjs` argument to Node.js.
630630
631-
When hooks are used they only apply to ES module loading and not to any
632-
CommonJS modules loaded.
631+
When hooks are used they apply to the entry point and all `import` calls. They
632+
won't apply to `require` calls; those still follow [CommonJS][] rules.
633633
634634
### Hooks
635635

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.