fix(pkg): add types to the exports
#125
Merged
+1
−0
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
in node16/nodenext module mode of TyepScript 4.7+, If package has `exports` entry on package.json, needs "types" field in `exports.*` for find typings. ref. https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/
|
Thanks for the PR. I agree to start adding |
pi0
changed the title
types to the exports
|
yes, in node16/nodenext mode, if
|
|
Thanks for confirming 👍🏼 |
pi0
changed the title
types to the exportstypes to the exports
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.
in node16/nodenext module mode of TyepScript 4.7+, If package has
exportsentry on package.json, needs "types" field inexports.*for find typings.ref. https://devblogs.microsoft.com/typescript/announcing-typescript-4-7/