doc: clarify entry point behavior when using loader hooks · nodejs/node@014d483 · GitHub

nodejs / node Public

• Notifications You must be signed in to change notification settings
• Fork 36.6k
• Star 120k

• Code
• Issues 637
• Pull requests 761
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Commit 014d483

Browse filesBrowse the repository at this point in the historyBrowse files

aduh95

authored and

targos

committed

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

1 file changed

+2-2Lines changed: 2 additions & 2 deletions

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• doc/api
  • esm.md

Expand file treeCollapse file tree

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 number	Diff line number	Diff line change
@@ -628,8 +628,8 @@ node b.mjs # works
628	628	To customize the default module resolution, loader hooks can optionally be
629	629	provided via a `--experimental-loader ./loader-name.mjs` argument to Node.js.
630	630
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.
633	633
634	634	### Hooks
635	635

0 commit comments

Comments

0 (0)