[PLAT-8122] Step towards Next.js 16 / React 19 upgrade - #223
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
aeischeid
changed the title
aeischeid
changed the title
|
aeischeid
changed the title
aeischeid
marked this pull request as ready for review
April 20, 2026 19:30
amvertex
approved these changes
Apr 20, 2026
| // Disable minifying with SWC until | ||
| // https://github.com/vercel/next.js/discussions/30237#discussioncomment-2950246 | ||
| // is resolved. | ||
| swcMinify: false, |
Contributor
There was a problem hiding this comment.
That's been there a long time 🙃
amvertex
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
I am exploring react19 compat - which comes along with nextJs v 16 -
this PR bumps a handful of things to modernize / stabilize a bit prior to making that major version jump
Test Plan
test locally
explore on vercel deployment
Release Notes
new version of yarn used. via corepack
Possible Regressions
as a starter project this is sort of not really a regression, as users wouldn't typically re-start within the same project, but considering a move from pages dir to app dir to follow new recommendation for NextJS so if you started a project previously the structure of a freshly started project would look a bit different. - a thing worth considering.
deciding to leave it as pages within this PR. move to app dir can be it's own initiative
Dependencies
yarn 4
typescript 5
node 22