Skip to content

Migrate to Next.js 16#684

Open
valentin0h wants to merge 3 commits intodevfrom
upgrade-nextjs16
Open

Migrate to Next.js 16#684
valentin0h wants to merge 3 commits intodevfrom
upgrade-nextjs16

Conversation

@valentin0h
Copy link
Collaborator

@valentin0h valentin0h commented Feb 26, 2026

Summary

  • Upgrade Next.js from 15.3.8 to 16.1.6
  • Upgrade next-intl from 4.1.0 to 4.8.3 (adds Next.js 16 support)
  • Update react/react-dom to ^19.2.0, @types/react to 19.2.14
  • Update @next/bundle-analyzer to ^16.0.0
  • Rename middleware.tsproxy.ts (Next.js 16 middleware API change)
  • Move experimental.serverComponentsExternalPackages → top-level serverExternalPackages
  • Remove deprecated experimental.instrumentationHook (now stable)
  • Add --webpack flag to dev/build scripts (required for custom webpack config with unplugin-icons, which doesn't support Turbopack yet)

- Update next from 15.3.8 to 16.1.6 in pnpm catalog
- Update react/react-dom to ^19.2.0, @types/react to 19.2.14
- Update @next/bundle-analyzer to ^16.0.0
- Rename middleware.ts → proxy.ts and export function middleware → proxy
- Move experimental.serverComponentsExternalPackages → serverExternalPackages
- Remove deprecated experimental.instrumentationHook (now stable)
- Add --webpack flag to dev/build scripts (required for custom webpack
  config with unplugin-icons which doesn't support Turbopack yet)
@vercel
Copy link
Contributor

vercel bot commented Feb 26, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
app Error Error Feb 26, 2026 3:50pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant