Skip to content

Commit 721def6

Browse files
Update next-intlayer reference in i18n doc (#83761)
[`next-intlayer`](https://intlayer.org/doc/environment/nextjs) is an i18n library that adopts a per-component approach to manage multilingual content in a next.js application. ### Changes - Fix doc related to page-router documentation, - And add App Router realted doc. Co-authored-by: Joseph <[email protected]>
1 parent deee6f3 commit 721def6

File tree

2 files changed

+2
-1
lines changed

2 files changed

+2
-1
lines changed

docs/01-app/02-guides/internationalization.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -215,3 +215,4 @@ export default async function RootLayout({ children, params }) {
215215
- [`paraglide-next`](https://inlang.com/m/osslbuzt/paraglide-next-i18n)
216216
- [`lingui`](https://lingui.dev)
217217
- [`tolgee`](https://tolgee.io/apps-integrations/next)
218+
- [`next-intlayer`](https://intlayer.org/doc/environment/nextjs)

docs/02-pages/02-guides/internationalization.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ description: Next.js has built-in support for internationalized routing and lang
1313

1414
Next.js has built-in support for internationalized ([i18n](https://en.wikipedia.org/wiki/Internationalization_and_localization#Naming)) routing since `v10.0.0`. You can provide a list of locales, the default locale, and domain-specific locales and Next.js will automatically handle the routing.
1515

16-
The i18n routing support is currently meant to complement existing i18n library solutions like [`react-intl`](https://formatjs.io/docs/getting-started/installation), [`react-i18next`](https://react.i18next.com/), [`lingui`](https://lingui.dev/), [`rosetta`](https://github.com/lukeed/rosetta), [`next-intl`](https://github.com/amannn/next-intl), [`next-translate`](https://github.com/aralroca/next-translate), [`next-multilingual`](https://github.com/Avansai/next-multilingual), [`tolgee`](https://tolgee.io/integrations/next), [`paraglide-next`](https://inlang.com/m/osslbuzt/paraglide-next-i18n), [`next-intlayer`](https://intlayer.org/doc/environment/nextjs) and others by streamlining the routes and locale parsing.
16+
The i18n routing support is currently meant to complement existing i18n library solutions like [`react-intl`](https://formatjs.io/docs/getting-started/installation), [`react-i18next`](https://react.i18next.com/), [`lingui`](https://lingui.dev/), [`rosetta`](https://github.com/lukeed/rosetta), [`next-intl`](https://github.com/amannn/next-intl), [`next-translate`](https://github.com/aralroca/next-translate), [`next-multilingual`](https://github.com/Avansai/next-multilingual), [`tolgee`](https://tolgee.io/integrations/next), [`paraglide-next`](https://inlang.com/m/osslbuzt/paraglide-next-i18n), [`next-intlayer`](https://intlayer.org/doc/environment/nextjs/next-with-page-router) and others by streamlining the routes and locale parsing.
1717

1818
## Getting started
1919

0 commit comments

Comments
 (0)