[legacy-framework] Fix duplicate image types (requires adding line to global.d.ts) #2597
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.
This PR attempts to fix the duplicate image types present in
next/types/global
that have since been stripped out and migrated tonext/image-types/global
. This, as a byproduct, uses the correct new svg typings inimage-types
that uses anany
type instead ofStaticImageData
.Correct
next/types/global
: https://github.com/vercel/next.js/blob/canary/packages/next/types/global.d.tsCorrect
next/image-types/global
: https://github.com/vercel/next.js/blob/canary/packages/next/image-types/global.d.ts