Skip to content
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

Jump to bottom

doc: clarify extensionless esm #30657

Closed
wants to merge 5 commits into from
Closed

doc: clarify extensionless esm #30657

Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e622474
doc: clarify required flag for extensionless esm
azz Nov 26, 2019
26b4cb9
doc: clarify extensionless file imports
azz Dec 3, 2019
bb49307
doc: reword extensionless definition
azz Dec 5, 2019
e05c651
doc: reword clarification
azz Dec 7, 2019
ff75ccb
doc: remove "note that"
azz Dec 16, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 2 additions & 1 deletion doc/api/esm.md
View file
Open in desktop
Expand Up @@ -84,7 +84,8 @@ If the nearest parent `package.json` lacks a `"type"` field, or contains
`"type": "commonjs"`, extensionless and `.js` files are treated as CommonJS.
If the volume root is reached and no `package.json` is found,
Node.js defers to the default, a `package.json` with no `"type"`
field.
field. Note that "extensionless" refers to file paths which do not contain
azz marked this conversation as resolved.
Show resolved Hide resolved
an extension as opposed to optionally dropping a file extension in a specifier.

`import` statements of `.js` and extensionless files are treated as ES modules
if the nearest parent `package.json` contains `"type": "module"`.
Expand Down