Repository navigation
Official First-Party Support for Internationalization i18n Features #95110
Replies: 2 comments 1 reply
|
I think this depends a lot on what we mean by “i18n support”. Pages Router did have something closer to a built-in i18n API, mainly around routing. But from the feedback the team collected back then, it seemed like many apps still had to customize or work around it once they needed specific locale detection behavior, fallback logic, URL structures, translation loading, CMS integration, pluralization, interpolation, type safety, etc. So while the Pages Router API looked more “complete” on the surface, a non-trivial number of projects still ended up customizing the i18n layer anyway. App Router gives you primitives to build the setup that fits your app. And this is also an area where the primitives can keep improving. For example, with upcoming root params support, accessing something like a locale segment from shared server code won't need prop drilling it through every layout/page boundary. I do think a setup option, example, or starter template could help reduce friction. But I’d be careful about framing this as first-party multilingual support unless the scope is clear. Things like routing conventions, locale-aware examples, proxy patterns, and primitives like root-params feel like a good fit for Next.js, while message formatting, pluralization, interpolation, extraction, translation management, and type-safety choices feel more like things specialised libraries are better suited for. |
|
It would have been much easier if Next.js provided an option during the 'npx create-next-app' setup to simply enable internationalization by ticking selecting 'yes'. If it automatically handled the foundational i18n setup, developers wouldn't have to go through the hassle and extra configurations required to set it up manually. |
Uh oh!
There was an error while loading. Please reload this page.
Goals
Provide seamless, first-party support for multilingual applications within Next.js.
Introduce an option during the setup process to enable i18n features, allowing developers to opt-in to localization support without needing external setups.
Reduce the friction and configuration overhead associated with third-party i18n libraries
Non-Goals
No response
Background
While Next.js provides some built-in routing capabilities for internationalization, there isn't a comprehensive, first-party solution for managing multilingual content. Developers often have to rely on third-party libraries or complex custom configurations, particularly with the App Router, which increases overhead and configuration complexity
Proposal
Provide seamless, first-party support for multilingual applications within Next.js; introduce an option during the setup process to enable i18n features, allowing developers to opt-in to localization support without needing external setups; and reduce the friction and configuration overhead associated with third-party i18n libraries
All reactions