[PLAT-8122] upgrade framework - Next v16.2 & React 19.2 #224
[PLAT-8122] upgrade framework - Next v16.2 & React 19.2 #224
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| "react/jsx-runtime": path.join(process.cwd(), "node_modules/react/jsx-runtime"), | ||
| "react/jsx-dev-runtime": path.join( | ||
| process.cwd(), | ||
| "node_modules/react/jsx-dev-runtime" | ||
| ), |
There was a problem hiding this comment.
these entries are here to keep mismatch version of react from local @vertexvis/viewer-react from conflicting. Could be commented out or maybe added as instruction for local sdk testing in readme 🤔
| "build:turbopack": "next build", | ||
| "clean": "rm -rf .next/ node_modules/", | ||
| "dev": "next", | ||
| "dev": "next dev --webpack", |
There was a problem hiding this comment.
new Next.js wants turbopack. Something with local yarn linking was really not liking turbopack, but seems to work fine when that isn't in play
| - [Vercel](https://nextjs.org/docs/deployment) | ||
| - [Netlify](https://www.netlify.com/blog/2020/11/30/how-to-deploy-next.js-sites-to-netlify/) | ||
| - [AWS CDK](https://github.com/serverless-nextjs/serverless-next.js#readme) | ||
| - [AWS via OpenNext](https://opennext.js.org) |
There was a problem hiding this comment.
serverless-next is dead project 😿 . superseded in spirit by OpenNext
| const nextUrl = encodeCreds(credentials); | ||
| if (router.asPath === nextUrl) return; | ||
|
|
||
| void router.replace(nextUrl, undefined, { shallow: true }); |
There was a problem hiding this comment.
Nope, shouldn't. Will clean
|
2 participants
Summary
Move the framework version up to Next 16 and also React to v 19
Test Plan
One goal of this upgrade is to test react19 compatibility coming in web-sdk. On deployed contexts will need newly released version of vertex-web-sdk to be available, which we don't have a definitive timeline on yet, but we're actively working on it and making good progress, so hopefully coming soon
Release Notes
Should be compatible with Vertexvis/vertex-web-sdk#729
Possible Regressions
While using older versions of vertex-web-sdk (< 0.25.x ?) may see complaints about unmatched peerDependencies, but in initial testing I haven't yet seen anything that is actually broken
Dependencies
New versions of esLint along for the ride