Skip to content

doc: highlight difference in module loading between ESM and CommonJS #59815

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

Merged
merged 1 commit into from
Nov 8, 2025
Merged

doc: highlight difference in module loading between ESM and CommonJS #59815

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 6 additions & 0 deletions doc/api/esm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -332,6 +332,12 @@ syncBuiltinESMExports();
fs.readFileSync === readFileSync;
```

> When importing built-in modules, all the named exports (i.e. properties of the module exports object)
> are populated even if they are not individually accessed.
> This can make initial imports of built-in modules slightly slower compared to loading them with
> `require()` or `process.getBuiltinModule()`, where the module exports object is evaluated immediately,
> but some of its properties may only be initialized when first accessed individually.
## `import()` expressions

[Dynamic `import()`][] provides an asynchronous way to import modules. It is
Expand Down