You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Next.js 16.3 exposes the `[locale]` root segment to Server Components via
`next/root-params`, which next-intl reads directly as of 4.13. That removes the
`setRequestLocale` bookkeeping the app needed for static rendering, along with
the locale threading through every page's `params`.
- `i18n.tsx` resolves the locale from the root param, so `requestLocale` is no
longer needed. An explicit locale passed by a call site still wins, which
stays useful for Server Actions and Route Handlers, where `next/root-params`
is not supported yet
- the root layout and `generateMetadata` read the locale via `getLocale()`,
which returns the already validated value from `i18n.tsx`
- `getLocaleAndPath` reads the root param itself instead of taking the locale
as an argument, so pages only destructure their own path segments. It keeps
reading `next/root-params` rather than `getLocale()` so that it still sees
the raw segment, which its notFound/redirect validation depends on
- the root layout no longer receives `params`
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
0 commit comments