-
Notifications
You must be signed in to change notification settings - Fork 59
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
fix!: use Node16 module resolution #1434
Open
achingbrain
wants to merge
3
commits into
main
Choose a base branch
from
fix/use-node16-resolution
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
This is to support the `"types"` field in `package.json` to support modules that no longer have a root `"types"` field.
achingbrain
changed the title
fix: use Node16 module resolution
fix!: use Node16 module resolution
Dec 30, 2023
achingbrain
added a commit
that referenced
this pull request
Jan 12, 2024
These deps don't work with `Node16` module resolution and PRs to fix this have been open for ages. Unblocks #1434
achingbrain
added a commit
that referenced
this pull request
Jan 12, 2024
These deps don't work with `Node16` module resolution and PRs to fix this have been open for ages. Unblocks #1434
SgtPooki
approved these changes
Apr 3, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we probably need to clean up quotations to be consistent
We need to test this thoroughly before merging - every dep needs a types entry for every export |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is to support the
"types"
field inpackage.json
to support modules that no longer have a root"types"
field.BREAKING CHANGE: Node16 module resolution ignores "types" and "typesVersions" in the
package.json
root when an exports map is found so requires "types" on every exports map entry instead