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

doc: esm: improve dual package hazard docs #30345

Closed
wants to merge 9 commits into from
Closed

doc: esm: improve dual package hazard docs #30345

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
c469d4b
doc: esm: improve dual package hazard docs
GeoffreyBooth Nov 9, 2019
6526130
doc: esm: remove example from hazard section
GeoffreyBooth Nov 11, 2019
1f7b577
doc: esm: revisions per feedback
GeoffreyBooth Nov 12, 2019
c9b6df3
doc: esm: give "main" a heading, mention other entry points
GeoffreyBooth Nov 13, 2019
2637f4d
doc: esm: add intro to package entry points section
GeoffreyBooth Nov 14, 2019
4b75b64
doc: rename for clarity
GeoffreyBooth Nov 14, 2019
a0d7c99
doc: merge intro language
GeoffreyBooth Nov 14, 2019
94e85ab
doc: typo
GeoffreyBooth Nov 16, 2019
912f281
doc: typo
GeoffreyBooth Nov 16, 2019
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: merge intro language
  • Loading branch information
@GeoffreyBooth
GeoffreyBooth committed Nov 14, 2019
commit a0d7c997637a647231862025c2c70908954a4592
23 changes: 7 additions & 16 deletions doc/api/esm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,14 +187,13 @@ unspecified.
There are two fields that can define entry points for a package: `"main"` and
`"exports"`. The `"main"` field is supported in all versions of Node.js, but its
capabilities are limited: it only defines the main entry point of the package.
The `"exports"` field can also be used to define the main entry point of the
package, as well as other defined entry points; and the package can be
encapsulated, so that extra effort is required to reference files within the
package that aren’t the defined public API. `"exports"` can also map an entry
point to different files per environment, for example for all environments
versus browser environments; and with `--experimental-conditional-exports`
`"exports"` can define separate files for Node.js CommonJS and ES module
environments.
The `"exports"` field, part of [Package Exports][], provides an alternative to
`"main"` where the package main entry point can be defined while also
encapsulating the package, preventing any other entry points besides those
defined in `"exports"`. If package entry points are defined in both `"main"` and
`"exports"`, the latter takes precedence in versions of Node.js that support
`"exports"`. [Conditional Exports][] can also be used within `"exports"` to
define different package entry points per environment.

#### <code>package.json</code> <code>"main"</code>

Expand Down Expand Up @@ -233,14 +232,6 @@ The `"main"` field can point to exactly one file, regardless of whether the
package is referenced via `require` (in a CommonJS context) or `import` (in an
ES module context).

[Package Exports][] provide an alternative to `"main"` where the package main
entry point can be defined while also encapsulating the package, preventing any
other entry points besides those defined in `"exports"`. If package entry points
are defined in both `"main"` and `"exports"`, the latter takes precedence in
versions of Node.js that support `"exports"`. [Conditional Exports][] can also
be used within `"exports"` to define different package entry points per
environment.

#### Package Exports

By default, all subpaths from a package can be imported (`import 'pkg/x.js'`).
Expand Down