[dev-2.0] fix: fix exports field in package.json
#8056
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sevenc-nanashi
changed the title
exports field in package.jsonexports field in package.json
sevenc-nanashi
force-pushed
the
v2/fix/es-exports
branch
from
557dbfd to
8e15927
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Changes:
This PR fixes
exportsfield in package.json.Currently,
tscignorestypesfield in package.json if there isexportsfield. This PR fixes this issue by adding definition of each entrypoints.This PR is forked from #8055 to edit files under
utils/, so it cannot be merged yet, but it's ready for review. (557dbfd is the first commit of this branch)Screenshots of the change:
PR Checklist
npm run lintpasses