docs: Add next-i18n-router as a resource for internationalized routing
#52344
Conversation
This file contains 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
Many developers are asking how to add internationalized routing with the App Router as it works with the Pages Router. The next-i18n-router library is a very helpful resource. Unlike the example provided in these Next.js i18n docs, next-i18n-router does not require nesting all pages in a [lang] dynamic segment. It also allows for the default language to be accessible without a locale prefix in the path (just like in the Pages Router). Also like the Pages Router, this library lets developers use the NEXT-LOCALE cookie to set a user's preferred language.
leerob
previously approved these changes
Aug 24, 2023
leerob
changed the title
next-i18n-router as a resource for internationalized routing
leerob
approved these changes
Aug 24, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Why?
Many developers are asking how to add internationalized routing in the App Router as it works in the Pages Router. next-i18n-router is a very helpful package that fully solves this challenge.
How?
Unlike the example provided in these Next.js i18n docs, next-i18n-router does not require nesting all pages in a
[lang]dynamic segment. It also allows for the default language to be accessible without a locale prefix in the path (just like in the Pages Router).It includes locale detection based on the
accept-languageheader as recommended in the Next.js docs, as well as support for theNEXT_LOCALEcookie to set a user's preferred language (just like in the Pages Router).