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 reads the locale via `getLocale()`, which returns the already
validated value from `i18n.tsx`, and no longer receives `params`
- `generateMetadata` and `getLocaleAndPath` read `next/root-params` directly
rather than `getLocale()`, because they need the raw segment: `getLocale()`
returns the already defaulted value, which would change the metadata emitted
for unknown and disabled locales and make the notFound/redirect validation in
`getLocaleAndPath` unreachable
0 commit comments