Update Next.js to v13 #1261
Merged
Update Next.js to v13 #1261
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
Belco90
force-pushed
the
upgrade_next_v13
branch
from
fece527
to
073461f
Compare
Belco90
force-pushed
the
upgrade_next_v13
branch
from
fe5bc7d
to
4084ff8
Compare
1 task
It's true by default on Next.js v13
Mainly adds legacyBehavior to avoid removing the anchor child. Auomatically transformed by Next.js codemode
Belco90
force-pushed
the
upgrade_next_v13
branch
from
ff9deda
to
d4cf274
Compare
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.
Changes
next/future/imagetonext/imagebrowsersListForSwcconfig option (BREAKING CHANGE: RemovebrowsersListForSwcand change default tolegacyBrowsers: falsevercel/next.js#41529)legacyBehaviorfor linksContext
n/a
Tests
I've checked my work by: