Skip to content

doc: fix explanation of package.json "type" field #27516

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

Closed
tamias wants to merge 3 commits into from
+6 −3
Closed

doc: fix explanation of package.json "type" field #27516

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fccd01b
doc: fix explanation of package.json "type" field
tamias May 1, 2019
1d63497
doc: further clarify package.json "type" field
tamias Dec 31, 2019
011fe06
doc: change "CommonJS modules" to "CommonJS"
tamias Jan 2, 2020
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
Prev Previous commit
Next Next commit
doc: further clarify package.json "type" field 
Added sentence about the type field not affecting .mjs and .cjs files.
  • Loading branch information
@tamias
tamias committed Dec 31, 2019
commit 1d6349746945f535570423555f612538bbcc5260
3 changes: 3 additions & 0 deletions doc/api/esm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,6 +101,9 @@ future-proof the package in case the default type of Node.js ever changes, and
it will also make things easier for build tools and loaders to determine how the
files in the package should be interpreted.

Regardless of the value of the `"type"` field, `.mjs` files are always treated
as ES modules and `.cjs` files are always treated as CommonJS modules.
Comment thread
tamias marked this conversation as resolved.
Outdated

### Package Scope and File Extensions

A folder containing a `package.json` file, and all subfolders below that
Expand Down