meta: upgraded react 19 next 15.2 #7531
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
removed
the
github_actions:pull-request
|
Lighthouse Results
|
AugustinMauroy
approved these changes
Mar 1, 2025
github-actions
bot
removed
the
github_actions:pull-request
|
@nodejs/nodejs-website @nodejs/web-infra I'm expediting this, as this potentially blocks other migrations such as Cloudflare and what not. cc @dario-piotrowicz be aware of this change, rebase will be needed, and this is a good opportunity for us to investigate Next.js 15.2 is still compatible with our changes. |
github-actions
bot
removed
the
github_actions:pull-request
Unit Test Coverage Report
Unit Test Report
|
github-actions
bot
removed
the
github_actions:pull-request
|
This was quick, wow |
Yup, it is pretty much dependency updates and tiny fixes for said dep updates. This falls under the policy of things that can be expedited. |
5 tasks
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.
This PR upgrades all packages and ensures a smooth Next.js 15.2 and React 19 migration.
The gist of this upgrade is that some nested-dependencies/peerDependencies are still with types/react 18 and types/react-dm 18 which causes TypeScript to compute that the globally exposed React types (since some dependencies are doing declare globals which is discouraged) versus the imported ones are different.
Pretty much very little had to be updated, besides of just forcing our types.