Add "types" field to package.json "exports" #78
Merged
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.
In TypeScript 4.7, the
nodenext
andnode16
module resolution options were added to better support native ESM in Node.js. When thepackage.json
"exports"
field exists, however, they require a"types"
field to exist within each entrypoint, or else types won't be resolved when using one of these module resolution options.Currently, using this library with either of those settings throws the following TypeScript error:
This PR fixes this issue by adding the
"types"
field to"exports"
for the"./"
entrypoint. The same change is required for@splinetool/runtime
, but I couldn't find a link to a repository where I could submit the change.