fix: nexgen ts module resolutions #124
Merged
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
✅ Deploy Preview for kobalte ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Hi, thanks. |
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.
Defines
typesin the exports map, so that imports work when leveraging the newermoduleResolutiontsconfig values (nodenext, node16, bundler).More info: microsoft/TypeScript#52363
Note that some of the example PRs linked to from the TS issue above are adding
typesto each specific condition inside of exports. In my experiments just addingtypesto the root of the exports map resolved the issues 🤷♂️.Before (after, types work as expected):