refactor: upgrade Next.js 15.5 to 16.2 with next-intl v4#17898
Merged
Conversation
✅ Deploy Preview for ethereumorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
config ⚙️
pettinarip
force-pushed
the
refactor/nextjs-16-upgrade
branch
3 times, most recently
from
a7a45d5 to
9d8d420
Compare
…k config - Bump next to ^16.2.1, @sentry/nextjs to ^10.46.0, @next/bundle-analyzer to ^16.2.1 - Bump next-intl from v3 to v4.8.3 - Rename middleware.ts to proxy.ts with export renamed to proxy - Migrate unstable_cache to "use cache" directive with stable cacheLife/cacheTag - Replace export const revalidate in API routes with "use cache" + cacheLife() - Enable experimental.useCache (cacheComponents deferred — requires PPR adoption) - Fix next-intl v4 getTranslations API: add locale param or use string form - Fix useTranslation hook type incompatibility with v4 Translator type - Replace localeDetection: false with localeCookie: false - Update .lintstagedrc.js and lint scripts from next lint to eslint - Update Sentry ignoreTransactions from middleware to proxy - Remove automaticVercelMonitors (Vercel-only) - Add turbopack.rules for YAML, SVG, MD, MP3 loaders - Add serverExternalPackages for WalletConnect deps - Dev and build use --webpack (Turbopack blocked by Tailwind CSS compat)
pettinarip
force-pushed
the
refactor/nextjs-16-upgrade
branch
from
9d8d420 to
291db4e
Compare
pettinarip
commented
Mar 30, 2026
pettinarip
commented
Mar 30, 2026
pettinarip
commented
Mar 30, 2026
wackerow
reviewed
Mar 31, 2026
wackerow
approved these changes
Apr 1, 2026
Member
wackerow
left a comment
wackerow
left a comment
There was a problem hiding this comment.
Looks good! Couple notes, no blockers
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
middleware.ts→proxy.ts(Next.js 16 convention)next linttoeslint .(next lintremoved in v16)Key decisions
dev:turbo/build:turboTest plan
npx tsc --noEmitpasses (no new errors)pnpm build(webpack) succeedspnpm dev(webpack) starts cleanlypnpm build-storybooksucceeds@storybook/nextjs@8.6does not support Next.js 16 (next/configwas removed). Requires Storybook 10.3+ upgrade — tracked in follow-up PR.Follow-up PRs
@storybook/nextjs@8.6→10.3+for Next.js 16 compat)cacheComponents/ PPR adoption (aftercrypto.randomUUID()investigation)