doc: highlight module loading difference between import and require · nodejs/node@795f32b · GitHub

nodejs / node Public

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

• Code
• Issues 633
• Pull requests 750
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Commit 795f32b

Browse filesBrowse the repository at this point in the historyBrowse files

Ajay-2005

authored and

aduh95

committed

doc: highlight module loading difference between import and require

PR-URL: #59815 Reviewed-By: Chengzhong Wu <legendecas@gmail.com>

1 parent 2127754 commit 795f32b
Copy full SHA for 795f32b

1 file changed

+6Lines changed: 6 additions & 0 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

+6Lines changed: 6 additions & 0 deletions

• Display the source diff
• Display the rich diff

Original file line number	Diff line number	Diff line change
@@ -332,6 +332,12 @@ syncBuiltinESMExports();
332	332	fs.readFileSync === readFileSync;
333	333	```
334	334
	335	+ > When importing built-in modules, all the named exports (i.e. properties of the module exports object)
	336	+ > are populated even if they are not individually accessed.
	337	+ > This can make initial imports of built-in modules slightly slower compared to loading them with
	338	+ > `require()` or `process.getBuiltinModule()`, where the module exports object is evaluated immediately,
	339	+ > but some of its properties may only be initialized when first accessed individually.
	340	+
335	341	## `import()` expressions
336	342
337	343	[Dynamic `import()`][] provides an asynchronous way to import modules. It is

0 commit comments

Comments

0 (0)