docs(manifest): add documentation for exports field #6995
+214
−56
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's Changed
Manifest documentation mentions export without actually documenting
The
exportsfield inpackage.jsonwas mentioned in the manifest docs but not properly documented.This made it unclear to users how to define entry points, conditional exports, or subpath exports.
Closes #6909
...
How did I fix it?
I added documentation for the
exportsfield in the manifest schema.exportsas the recommended way to describe package entry points."."), subpaths ("./cli"), and conditional exports ("import","require").patternPropertiesfor flexibility....
Checklist