feat(i18n): adopt next/root-params - #9105
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
amannn
commented
Aug 14, 2026
5 tasks
amannn
force-pushed
the
feat/next-root-params
branch
from
August 14, 2026 12:45
32f79c9 to
a3cfe02
Compare
amannn
marked this pull request as ready for review
August 14, 2026 12:52
amannn
changed the title
next/root-params
Contributor
Author
|
@ovflowd @AugustinMauroy I thought you might be interested in adopting On a related note, I've been working on a new tool called |
Member
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9105 +/- ##
==========================================
+ Coverage 86.01% 86.13% +0.12%
==========================================
Files 86 86
Lines 6099 6051 -48
Branches 358 357 -1
==========================================
- Hits 5246 5212 -34
+ Misses 849 835 -14
Partials 4 4 ☔ View full report in Codecov by Harness. |
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
Contributor
📦 Build Size ComparisonSummary
|
amannn
force-pushed
the
feat/next-root-params
branch
from
August 14, 2026 13:35
a3cfe02 to
7bcaf09
Compare
Contributor
Author
Done! |
AugustinMauroy
approved these changes
Aug 14, 2026
AugustinMauroy
left a comment
AugustinMauroy
left a comment
Member
There was a problem hiding this comment.
LGTM that make thing cleaner
avivkeller
approved these changes
Aug 14, 2026
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
3 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.
Description
Next.js 16.3 ships with
next/root-params, which is a significant improvement for users ofnext-intl.See the introductory blog post: Using next/root-params in Next.js 16.3
I went ahead to see how this integrates with nodejs.org, and it seems to work well!
Validation
I checked various languages and also different 404 states.
Related Issues
None.
Check List
pnpm formatto ensure the code follows the style guide.pnpm testto check if all tests are passing.pnpm buildto check if the website builds without errors.