Add types exports to the package.json #3
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
|
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.
The new TypeScript moduleResolutions
node16/nodenext/bundlerrequire types declarations for packages that haveexports.This resolves the error
TS7016: Could not find a declaration file for module 'mantine-flagpack'. '/node_modules/mantine-flagpack/dist/esm/index.js' implicitly has an 'any' type. There are types at '/node_modules/mantine-flagpack/declarations/index.d.ts', but this result could not be resolved when respecting package.json "exports". The 'mantine-flagpack' library may need to update its package.json or typings.Reference: microsoft/TypeScript#52363