chore: declare types in package.json conditional exports #5
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
Fixes importing this package in TypeScript. Before, it expected the types to live next to the CJS/ESM files mentioned in `exports`. However, the types live in a separate directory. With this change, TypeScript will use this new explicit "types" condition [0] to resolve types correctly. [0]: https://www.typescriptlang.org/docs/handbook/modules/reference.html#example-explicit-types-condition
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.
Fixes importing this package in TypeScript. Before, it expected the types to live next to the CJS/ESM files mentioned in
exports. However, the types live in a separate directory.With this change, TypeScript will use this new explicit "types" condition to resolve types correctly.