Fix types resolution #2084
Merged
Fix types resolution #2084
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
🦋 Changeset detectedLatest commit: 4faa800 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
connor-baer
added
the
🚢 ready to merge
Codecov Report
@@ Coverage Diff @@
## next #2084 +/- ##
=======================================
Coverage 96.91% 96.91%
=======================================
Files 258 258
Lines 23163 23163
Branches 2165 2165
=======================================
Hits 22449 22449
Misses 707 707
Partials 7 7 |
connor-baer
force-pushed
the
next
branch
2 times, most recently
from
5e3d899
to
321fee2
Compare
pdrmdrs
approved these changes
May 8, 2023
Closed
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.
Purpose
The package entry points are defined using the
exportsfield since #2061. TypeScript is supposed to be able to resolve the types relative to the path(s) defined in theexportsfield, but testing the latestnextrelease proves otherwise.Approach and changes
typesfield in thepackage.jsonfilesDefinition of done