Upgrade nextjs v13 to v14 #22152
Closed
Upgrade nextjs v13 to v14 #22152
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
|
Looks like some dependency issues as well: |
- Fixing missing peer dependencies
|
Closing this PR due to blockers with Buildkite and an unclear pathway to fix them. It looks like the Next version was bumped to 14+ on Master by another PR so the main goal of this PR has been accomplished. |
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.
Summary & Motivation
Upgrading Next.js to enable handling several features of the MDX-transform make script as automatic parts of Markdoc's transform step.
How I Tested These Changes
Ran on local. No build errors. No visible issues on a sample of Markdoc based and MDX based pages.