Skip to content
Closed
Changes from 1 commit
Commits
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
Update doc/api/esm.md
Co-Authored-By: Rob Palmer <rob.palmer2@gmail.com>
  • Loading branch information
MylesBorins and robpalme authored Apr 28, 2020
commit 2acd4262109229266872d94e6fdf8f1a0a201e36
6 changes: 4 additions & 2 deletions doc/api/esm.md
Original file line number Diff line number Diff line change
Expand Up @@ -194,8 +194,10 @@ environment, including whether the package is referenced via `require` or via
**Warning**: Introducing the `"exports"` field prevents consumers of a package
from using any entry points that are not defined, including the `package.json`.
This will likely be a breaking change. To make the introduction of `"exports"`
non-breaking, either ensure that every previously supported entry point is
exported or include an export of the root of the package `"./": "./"`.
non-breaking, ensure that every previously supported entry point is exported.
It is best to explicitly specify entry points so that the package's public API is
well-defined. As a last resort, package encapsulation can be disabled entirely by
Comment thread
MylesBorins marked this conversation as resolved.
Outdated
creating an export for the root of the package `"./": "./"` that will expose every file.

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