Repository navigation
Official First-Party Support for Internationalization Features #95109
Closed
mdnoyun198
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Goals
1.Provide seamless, first-party support for multilingual applications within Next.js
2.Introduce an option during the setup process to enable i18n features, allowing developers to opt-in to localization support without needing external setups
3.Reduce the friction and configuration overhead associated with third-party i18n libraries.
Non-Goals
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
rovide 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