Merge new doc under next 14 in 5.x branch #1977
Merged
Conversation
This file contains hidden or 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
…ructors (#1974) * Upgrade eslint and ignore no-constructor-return rule for actual constructors * ignore eslint-next for now
* upgrate to next 12 * next 13 * migrate links * next 14 * deactivate eslint for documentation once again * Fix title warning. See vercel/next.js#38256
jdeniau
changed the title
jdeniau
force-pushed
the
5.x-merge-main-new-doc
branch
from
2498837 to
b1f49e6
Compare
jdeniau
force-pushed
the
5.x-merge-main-new-doc
branch
from
b1f49e6 to
c536b78
Compare
jdeniau
force-pushed
the
5.x-merge-main-new-doc
branch
from
c536b78 to
8058d92
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.
There is an issue while merging main into 5.x on package-lock.json file.