-
Notifications
You must be signed in to change notification settings - Fork 10
Bump next from 14.2.32 to 16.1.0 #1605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,7 +15,7 @@ | |
| "@segment/analytics-next": "^1.81.1", | ||
| "@vercel/og": "^0.8.5", | ||
| "classnames": "^2.5.1", | ||
| "next": "^14.2.32", | ||
| "next": "^16.1.1", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. eslint-config-next version mismatches Next.js 16The |
||
| "mixpanel-browser": "^2.64.0", | ||
| "nextra": "^3.1.0", | ||
| "nextra-theme-docs": "^3.3.1", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Next.js 16 requires React 19 but React 18 remains
Upgrading
nextfrom 14.2.32 to 16.1.1 without upgrading React introduces a peer dependency incompatibility. Next.js 16 requires React 19, but the project still usesreactandreact-domat version^18.3.1. This major version mismatch will likely cause runtime errors or application failure. React and React DOM need to be upgraded to version 19 alongside the Next.js upgrade.