Update logic around next/future/image
#20173
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
Co-authored-by: Valentin Palkovic <[email protected]>
kylegach
force-pushed
the
nextjs-image-fix
branch
from
dbbb9ea to
675ab2b
Compare
valentinpalkovic
approved these changes
Dec 8, 2022
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.
What I did
Currently, the logic to ignore imports of
next/future/image(introduced in12.2and removed in13) does not apply correctly when using a version of next between12(inclusive) and12.2(exclusive), e.g.12.1.5.This PR updates the logic.
Related PR: #20098
How to test
If your answer is yes to any of these, please make sure to include it in your PR.