Update package.json - add types to exports #677
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
when changing moduleResolution from node to bundler (as in https://github.com/vercel/next.js/pull/51957/files#diff-066cacecd32e0ca72d47360ddb35c19a676835816eed05163e05564ec0874590)in tsconfig.json following errors occurs: ./pages/sitemap.xml/index.tsx:2:36 Type error: Could not find a declaration file for module 'next-sitemap'. 'C:/dev/frontend/project/node_modules/next-sitemap/dist/esm/index.js' implicitly has an 'any' type. There are types at 'C:/dev/frontend/project/node_modules/next-sitemap/dist/@types/index.d.ts', but this result could not be resolved when respecting package.json "exports". The 'next-sitemap' library may need to update its package.json or typings. 1 | import type { GetServerSideProps } from "next"; > 2 | import type { ISitemapField } from "next-sitemap"; The error can be fixed via copying the types to the exports "." section in package.json (as described here: https://stackoverflow.com/a/76212193/1548552)
|
Someone is attempting to deploy a commit to a Personal Account owned by @iamvishnusankar on Vercel. @iamvishnusankar first needs to authorize it. |
|
This is much needed, when should we see the updated one? |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
|
Hi, |
we need this asap as the site is suffering from this issue |
|
Any update on this? |
iamvishnusankar
approved these changes
Sep 6, 2023
ariesclark
pushed a commit
to ariesclark/next-sitemap-x
that referenced
this pull request
Dec 14, 2024
Update package.json - add types to 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.
when changing moduleResolution from
nodetobundler(as in https://github.com/vercel/next.js/pull/51957/files#diff-066cacecd32e0ca72d47360ddb35c19a676835816eed05163e05564ec0874590) in tsconfig.json, the following errors occur during build:The error can be fixed by copying the types to the exports "." section in package.json (as described here: https://stackoverflow.com/a/76212193/1548552)