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.

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: update to package.exports docs #33074

Closed
wants to merge 24 commits into from
Closed
Changes from 1 commit
Commits
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
6 changes: 6 additions & 0 deletions doc/api/esm.md
Expand Up @@ -191,6 +191,12 @@ also be used within `"exports"` to define different package entry points per
environment, including whether the package is referenced via `require` or via
`import`.

***Warning***: Introducing the exports field prevents consumers of a package
MylesBorins marked this conversation as resolved.
Show resolved Hide resolved
for using any entry points that is not defined, including the `package.json`.
MylesBorins marked this conversation as resolved.
Show resolved Hide resolved
This is a Semver-Major change. To make the introduction of `"exports"`
MylesBorins marked this conversation as resolved.
Show resolved Hide resolved
MylesBorins marked this conversation as resolved.
Show resolved Hide resolved
Semver-Minor either ensure that every previously supported entry point is
MylesBorins marked this conversation as resolved.
Show resolved Hide resolved
exported or include a export of the root of the package `"./"; "./"`.
MylesBorins marked this conversation as resolved.
Show resolved Hide resolved

If both `"exports"` and `"main"` are defined, the `"exports"` field takes
precedence over `"main"`.

Expand Down