@intlayer/docs 6.1.5 → 6.1.6

package/blog/en/next-i18next_vs_next-intl_vs_intlayer.md

@@ -19,6 +19,8 @@ slugs:
 
 # next-i18next VS next-intl VS intlayer | Next.js Internationalization (i18n)
 
+![next-i18next VS next-intl VS intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/assets/i18next-next-intl-intlayer.png?raw=true)
+
 Let’s take a look into the similarities and differences between three i18n options for Next.js: next-i18next, next-intl, and Intlayer.
 
 This is not a full tutorial. It’s a comparison to help you pick.
@@ -35,7 +37,7 @@ We focus on **Next.js 13+ App Router** (with **React Server Components**) and ev
 
 > **tl;dr**: All three can localize a Next.js app. If you want **component-scoped content**, **strict TypeScript types**, **build-time missing-key checks**, **tree-shaken dictionaries**, and **first-class App Router + SEO helpers**, **Intlayer** is the most complete, modern choice.
 
-> One confusion often made by developers is to think that `next-intl` is the Next.js version of `react-intl`. It's not—`next-intl` is maintained by [Amann](https://github.com/amannn), while `react-intl` is maintained by [FormatJS](https://github.com/formatjs/formatjs).
+> One confusion often made by developers is to think that `next-intl` is the Next.js version of `react-intl`. It's not, `next-intl` is maintained by [Amann](https://github.com/amannn), while `react-intl` is maintained by [FormatJS](https://github.com/formatjs/formatjs).
 
 ---
 
@@ -163,11 +165,13 @@ How the library handles fallbacks is also important. Let's consider that the app
 
 In the case of `next-intl` and `next-i18next`, the library requires loading the JSON related to the current locale, but also to the fallback locale. Thus, considering that all content has been translated, each page will load 100% unnecessary content. **In comparison, `intlayer` processes the fallback at dictionary build time. Thus, each page will load only the content used.**
 
+> Note: To optimize the bundle using `intlayer`, you need to set the `importMode: 'dynamic'` option in your `intlayer.config.ts` file. And ensure the plugin `@intlayer/babel` / `@intlayer/swc` is installed (installed by default using `vite-intlayer`).
+
 Here an example of the impact of bundle size optimization using `intlayer` in a vite + react application:
 
-| Optimized bundle                                                                             | Bundle not optimized                                                                                            |
-| -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
-| ![optimized bundle](https://github.com/aymericzip/intlayer/blob/main/docs/assets/bundle.png) | ![no optimized bundle](https://github.com/aymericzip/intlayer/blob/main/docs/assets/bundle_no_optimization.png) |
+| Optimized bundle                                                                                      | Bundle not optimized                                                                                                     |
+| ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| ![optimized bundle](https://github.com/aymericzip/intlayer/blob/main/docs/assets/bundle.png?raw=true) | ![no optimized bundle](https://github.com/aymericzip/intlayer/blob/main/docs/assets/bundle_no_optimization.png?raw=true) |
 
 ---
 
@@ -176,16 +180,16 @@ Here an example of the impact of bundle size optimization using `intlayer` in a
 <Columns>
   <Column>
 
-**next-intl**
+**next-i18next**
 
-- Solid TypeScript support, but **keys aren’t strictly typed by default**; you’ll maintain safety patterns manually.
+- Base typings for hooks. **strict key typing requires extra tooling/config**.
 
   </Column>
   <Column>
 
-**next-i18next**
+**next-intl**
 
-- Base typings for hooks; **strict key typing requires extra tooling/config**.
+- Solid TypeScript support, but **keys aren’t strictly typed by default**. you’ll maintain safety patterns manually.
 
   </Column>
   <Column>
@@ -206,16 +210,16 @@ Here an example of the impact of bundle size optimization using `intlayer` in a
 <Columns>
   <Column>
 
-**next-intl**
+**next-i18next**
 
-- Relies on **runtime fallbacks** (e.g., show the key or default locale). Build doesn’t fail.
+- Relies on **runtime fallbacks**. Build doesn’t fail.
 
   </Column>
   <Column>
 
-**next-i18next**
+**next-intl**
 
-- Relies on **runtime fallbacks** (e.g., show the key or default locale). Build doesn’t fail.
+- Relies on **runtime fallbacks**. Build doesn’t fail.
 
   </Column>
   <Column>
@@ -227,7 +231,7 @@ Here an example of the impact of bundle size optimization using `intlayer` in a
   </Column>
 </Columns>
 
-**Why it matters:** Catching gaps during build prevents “mystery strings” in production and aligns with strict release gates.
+**Why it matters:** Catching gaps during build prevents 'undefined' strings in production.
 
 ---
 
@@ -236,28 +240,30 @@ Here an example of the impact of bundle size optimization using `intlayer` in a
 <Columns>
   <Column>
 
-**next-intl**
+**next-i18next**
 
-- Works with **Next.js localized routing** on the App Router.
+- Allows localized routing. But middleware is not built-in.
 
   </Column>
   <Column>
 
-**next-i18next**
+**next-intl**
 
-- Works with **Next.js localized routing** on the App Router.
+- Allows localized routing.
+- Provides middleware.
 
   </Column>
   <Column>
 
 **intlayer**
 
-- All of the above, plus **i18n middleware** (locale detection via headers/cookies) and **helpers** to generate localized URLs and `<link rel="alternate" hreflang="…">` tags.
+- Allows localized routing.
+- Provides middleware.
 
   </Column>
 </Columns>
 
-**Why it matters:** Fewer custom glue layers; **consistent UX** and **clean SEO** across locales.
+**Why it matters:** Helps for SEO and discovery, as well as user experience.
 
 ---
 
@@ -266,58 +272,33 @@ Here an example of the impact of bundle size optimization using `intlayer` in a
 <Columns>
   <Column>
 
-**next-intl**
-
-- Supports Next.js 13+. Often requires passing t-functions/formatters through component trees in hybrid setups.
-
-  </Column>
-  <Column>
-
 **next-i18next**
 
-- Supports Next.js 13+. Similar constraints with passing translation utilities across boundaries.
+- Support page and layout server components.
+- Do not provide synchronous API for children server components.
 
   </Column>
   <Column>
 
-**intlayer**
-
-- Supports Next.js 13+ and smooths the **server/client boundary** with a consistent API and RSC-oriented providers, avoiding shuttling formatters or t-functions.
-
-  </Column>
-</Columns>
-
-**Why it matters:** Cleaner mental model and fewer edge cases in hybrid trees.
-
----
-
-## DX, tooling & maintenance
-
-<Columns>
-  <Column>
-
 **next-intl**
 
-- Commonly paired with external localization platforms and editorial workflows.
-
-  </Column>
-  <Column>
-
-**next-i18next**
-
-- Commonly paired with external localization platforms and editorial workflows.
+- Support page and layout server components.
+- Do not provide synchronous API for children server components.
 
   </Column>
   <Column>
 
 **intlayer**
 
-- Ships a **free Visual Editor** and **optional CMS** (Git-friendly or externalized), plus a **VSCode extension** and **AI-assisted translations** using your own provider keys.
+- Support page and layout server components.
+- Provide synchronous API for children server components.
 
   </Column>
 </Columns>
 
-**Why it matters:** Lowers ops cost and shortens the loop between developers and content authors.
+**Why it matters:** Server component suport is a key feature of Next.js 13+, helping for performance. Passing props the locale or the `t` function from the parent to the child server components make your components less reusable.
+
+---
 
 ## Integration with localization platforms (TMS)
 
@@ -338,6 +319,8 @@ Large organizations often rely on Translation Management Systems (TMS) like **Cr
 
 > Note: `next-intl` and `i18next` also accepts TypeScript catalogs. If your team stores messages in `.ts` files or decentralizes them by feature, you can face similar TMS friction. However, many `next-intl` setups remain centralized in a `locales/` folder, which is a bit easier to refactor to JSON for TMS.
 
+---
+
 ## Developer Experience
 
 This part makes a deep comparison between the three solutions. Rather than considering simple cases, as described in the 'getting started' documentation for each solution, we will consider a real use case, more similar to a real project.
@@ -352,25 +335,25 @@ The app structure is important to ensure good maintainability for your codebase.
 
 ```bash
 .
-├── public
-│   └── locales
-│       ├── en
-│       │  ├── home.json
-│       │  └── navbar.json
-│       ├── fr
-│       │  ├── home.json
-│       │  └── navbar.json
-│       └── es
-│          ├── home.json
-│          └── navbar.json
-├── next-i18next.config.js
+├── i18n.config.ts
 └── src
-    ├── middleware.ts
+    ├── locales
+    │   ├── en
+    │   │  ├── common.json
+    │   │  └── about.json
+    │   └── fr
+    │      ├── common.json
+    │      └── about.json
     ├── app
-    │   └── home.tsx
+    │   ├── i18n
+    │   │   └── server.ts
+    │   └── [locale]
+    │       ├── layout.tsx
+    │       └── about.tsx
     └── components
-        └── Navbar
-            └── index.tsx
+        ├── I18nProvider.tsx
+        ├── ClientComponent.tsx
+        └── ServerComponent.tsx
 ```
 
   </TabItem>
@@ -378,6 +361,7 @@ The app structure is important to ensure good maintainability for your codebase.
 
 ```bash
 .
+├── i18n.ts
 ├── locales
 │   ├── en
 │   │  ├── home.json
@@ -388,11 +372,13 @@ The app structure is important to ensure good maintainability for your codebase.
 │   └── es
 │      ├── home.json
 │      └── navbar.json
-├── i18n.ts
 └── src
     ├── middleware.ts
     ├── app
-    │   └── home.tsx
+    │   ├── i18n
+    │   │   └── server.ts
+    │   └── [locale]
+    │       └── home.tsx
     └── components
         └── Navbar
             └── index.tsx
@@ -407,9 +393,11 @@ The app structure is important to ensure good maintainability for your codebase.
 └── src
     ├── middleware.ts
     ├── app
-    │   └── home
-    │       └── index.tsx
-    │       └── index.content.ts
+    │   └── [locale]
+    │       ├── layout.tsx
+    │       └── home
+    │           ├── index.tsx
+    │           └── index.content.ts
     └── components
         └── Navbar
             ├── index.tsx
@@ -432,141 +420,276 @@ How the library handles content loading is important.
 <Tab defaultTab="next-intl" group='techno'>
   <TabItem label="next-i18next" value="next-i18next">
 
-```tsx fileName="next-i18next.config.js"
-module.exports = {
-  i18n: {
-    locales: ["en", "fr", "es"],
-    defaultLocale: "en",
-  },
-};
-```
+```ts fileName="i18n.config.ts"
+export const locales = ["en", "fr"] as const;
+export type Locale = (typeof locales)[number];
 
-```tsx fileName="src/app/_app.tsx"
-import { appWithTranslation } from "next-i18next";
+export const defaultLocale: Locale = "en";
 
-const MyApp = ({ Component, pageProps }) => <Component {...pageProps} />;
+export const rtlLocales = ["ar", "he", "fa", "ur"] as const;
+export const isRtl = (locale: string) =>
+  (rtlLocales as readonly string[]).includes(locale);
 
-export default appWithTranslation(MyApp);
+export function localizedPath(locale: string, path: string) {
+  return locale === defaultLocale ? path : "/" + locale + path;
+}
+
+const ORIGIN = "https://example.com";
+export function abs(locale: string, path: string) {
+  return ORIGIN + localizedPath(locale, path);
+}
 ```
 
-```tsx fileName="src/app/[locale]/about/page.tsx"
-import type { GetStaticProps } from "next";
-import { serverSideTranslations } from "next-i18next/serverSideTranslations";
-import { useTranslation } from "next-i18next";
-import { I18nextProvider, initReactI18next } from "react-i18next";
+```ts fileName="src/app/i18n/server.ts"
 import { createInstance } from "i18next";
-import { ClientComponent, ServerComponent } from "@components";
+import { initReactI18next } from "react-i18next/initReactI18next";
+import resourcesToBackend from "i18next-resources-to-backend";
+import { defaultLocale } from "@/i18n.config";
+
+// Load JSON resources from src/locales/<locale>/<namespace>.json
+const backend = resourcesToBackend(
+  (locale: string, namespace: string) =>
+    import(`../../locales/${locale}/${namespace}.json`)
+);
+
+export async function initI18next(
+  locale: string,
+  namespaces: string[] = ["common"]
+) {
+  const i18n = createInstance();
+  await i18n
+    .use(initReactI18next)
+    .use(backend)
+    .init({
+      lng: locale,
+      fallbackLng: defaultLocale,
+      ns: namespaces,
+      defaultNS: "common",
+      interpolation: { escapeValue: false },
+      react: { useSuspense: false },
+    });
+  return i18n;
+}
+```
 
-export default function HomePage({ locale }: { locale: string }) {
-  // Déclarez explicitement le namespace utilisé par ce composant
-  const resources = await loadMessagesFor(locale); // your loader (JSON, etc.)
+```tsx fileName="src/components/I18nProvider.tsx"
+"use client";
 
-  const i18n = createInstance();
-  i18n.use(initReactI18next).init({
-    lng: locale,
-    fallbackLng: "en",
-    resources,
-    ns: ["common", "about"],
-    defaultNS: "common",
-    interpolation: { escapeValue: false },
+import * as React from "react";
+import { I18nextProvider } from "react-i18next";
+import { createInstance } from "i18next";
+import { initReactI18next } from "react-i18next/initReactI18next";
+import resourcesToBackend from "i18next-resources-to-backend";
+import { defaultLocale } from "@/i18n.config";
+
+const backend = resourcesToBackend(
+  (locale: string, namespace: string) =>
+    import(`../../locales/${locale}/${namespace}.json`)
+);
+
+type Props = {
+  locale: string;
+  namespaces?: string[];
+  resources?: Record<string, any>; // { ns: bundle }
+  children: React.ReactNode;
+};
+
+export default function I18nProvider({
+  locale,
+  namespaces = ["common"],
+  resources,
+  children,
+}: Props) {
+  const [i18n] = React.useState(() => {
+    const i = createInstance();
+
+    i.use(initReactI18next)
+      .use(backend)
+      .init({
+        lng: locale,
+        fallbackLng: defaultLocale,
+        ns: namespaces,
+        resources: resources ? { [locale]: resources } : undefined,
+        defaultNS: "common",
+        interpolation: { escapeValue: false },
+        react: { useSuspense: false },
+      });
+
+    return i;
   });
 
-  const { t } = useTranslation("about");
+  return <I18nextProvider i18n={i18n}>{children}</I18nextProvider>;
+}
+```
+
+```tsx fileName="src/app/[locale]/layout.tsx"
+import type { ReactNode } from "react";
+import { locales, defaultLocale, isRtl, type Locale } from "@/i18n.config";
+
+export const dynamicParams = false;
+
+export function generateStaticParams() {
+  return locales.map((locale) => ({ locale }));
+}
+
+export default function LocaleLayout({
+  children,
+  params,
+}: {
+  children: ReactNode;
+  params: { locale: string };
+}) {
+  const locale: Locale = (locales as readonly string[]).includes(params.locale)
+    ? (params.locale as any)
+    : defaultLocale;
+
+  const dir = isRtl(locale) ? "rtl" : "ltr";
+
+  return (
+    <html lang={locale} dir={dir}>
+      <body>{children}</body>
+    </html>
+  );
+}
+```
+
+```tsx fileName="src/app/[locale]/about.tsx"
+import I18nProvider from "@/components/I18nProvider";
+import { initI18next } from "@/app/i18n/server";
+import type { Locale } from "@/i18n.config";
+import ClientComponent from "@/components/ClientComponent";
+import ServerComponent from "@/components/ServerComponent";
+
+// Force static rendering for the page
+export const dynamic = "force-static";
+
+export default async function AboutPage({
+  params: { locale },
+}: {
+  params: { locale: Locale };
+}) {
+  const namespaces = ["common", "about"] as const;
+
+  const i18n = await initI18next(locale, [...namespaces]);
+  const tAbout = i18n.getFixedT(locale, "about");
 
   return (
-    <I18nextProvider i18n={i18n}>
+    <I18nProvider locale={locale} namespaces={[...namespaces]}>
       <main>
-        <h1>{t("title")}</h1>
+        <h1>{tAbout("title")}</h1>
+
         <ClientComponent />
-        <ServerComponent />
+        <ServerComponent t={tAbout} locale={locale} count={0} />
       </main>
-    </I18nextProvider>
+    </I18nProvider>
   );
 }
-
-export const getStaticProps: GetStaticProps = async ({ locale }) => {
-  // Ne préchargez que les namespaces nécessaires à CETTE page
-  return {
-    props: {
-      ...(await serverSideTranslations(locale ?? "en", ["common", "about"])),
-    },
-  };
-};
 ```
 
   </TabItem>
    <TabItem label="next-intl" value="next-intl">
 
-```tsx fileName="i18n.ts"
+```tsx fileName="src/i18n.ts"
 import { getRequestConfig } from "next-intl/server";
 import { notFound } from "next/navigation";
 
-// Can be imported from a shared config
-const locales = ["en", "fr", "es"];
+export const locales = ["en", "fr", "es"] as const;
+export const defaultLocale = "en" as const;
+
+async function loadMessages(locale: string) {
+  // Load only the namespaces your layout/pages need
+  const [common, about] = await Promise.all([
+    import(`../locales/${locale}/common.json`).then((m) => m.default),
+    import(`../locales/${locale}/about.json`).then((m) => m.default),
+  ]);
+
+  return { common, about } as const;
+}
 
 export default getRequestConfig(async ({ locale }) => {
-  // Validate that the incoming `locale` parameter is valid
   if (!locales.includes(locale as any)) notFound();
 
   return {
-    messages: (await import(`../messages/${locale}.json`)).default,
+    messages: await loadMessages(locale),
   };
 });
 ```
 
-```tsx fileName="src/app/[locale]/about/layout.tsx"
-import { NextIntlClientProvider } from "next-intl";
-import { getMessages, unstable_setRequestLocale } from "next-intl/server";
-import pick from "lodash/pick";
+```tsx fileName="src/app/[locale]/layout.tsx"
+import type { ReactNode } from "react";
+import { locales } from "@/i18n";
+import {
+  getLocaleDirection,
+  unstable_setRequestLocale,
+} from "next-intl/server";
+
+export const dynamic = "force-static";
+
+export function generateStaticParams() {
+  return locales.map((locale) => ({ locale }));
+}
 
 export default async function LocaleLayout({
   children,
   params,
 }: {
-  children: React.ReactNode;
-  params: { locale: string };
+  children: ReactNode;
+  params: Promise<{ locale: string }>;
 }) {
-  const { locale } = params;
+  const { locale } = await params;
 
   // Set the active request locale for this server render (RSC)
   unstable_setRequestLocale(locale);
 
-  // Messages are loaded server-side via src/i18n/request.ts
-  // (see next-intl docs). Here we only push a subset to the client
-  // that's needed for client components (payload optimization).
-  const messages = await getMessages();
-  const clientMessages = pick(messages, ["common", "about"]);
+  const dir = getLocaleDirection(locale);
 
   return (
-    <html lang={locale}>
-      <body>
-        <NextIntlClientProvider locale={locale} messages={clientMessages}>
-          {children}
-        </NextIntlClientProvider>
-      </body>
+    <html lang={locale} dir={dir}>
+      <body>{children}</body>
     </html>
   );
 }
 ```
 
 ```tsx fileName="src/app/[locale]/about/page.tsx"
-import { getTranslations } from "next-intl/server";
-import { ClientComponent, ServerComponent } from "@components";
+import { getTranslations, getMessages, getFormatter } from "next-intl/server";
+import { NextIntlClientProvider } from "next-intl";
+import pick from "lodash/pick";
+import ServerComponent from "@/components/ServerComponent";
+import ClientComponentExample from "@/components/ClientComponentExample";
 
-export default async function LandingPage({
+export const dynamic = "force-static";
+
+export default async function AboutPage({
   params,
 }: {
-  params: { locale: string };
+  params: Promise<{ locale: string }>;
 }) {
-  // Chargement strictement côté serveur (pas hydraté au client)
-  const t = await getTranslations("about");
+  const { locale } = await params;
+
+  // Messages are loaded server-side. Push only what's needed to the client.
+  const messages = await getMessages();
+  const clientMessages = pick(messages, ["common", "about"]);
+
+  // Strictly server-side translations/formatting
+  const tAbout = await getTranslations("about");
+  const tCounter = await getTranslations("about.counter");
+  const format = await getFormatter();
+
+  const initialFormattedCount = format.number(0);
 
   return (
-    <main>
-      <h1>{t("title")}</h1>
-      <ClientComponent />
-      <ServerComponent />
-    </main>
+    <NextIntlClientProvider locale={locale} messages={clientMessages}>
+      <main>
+        <h1>{tAbout("title")}</h1>
+        <ClientComponentExample />
+        <ServerComponent
+          formattedCount={initialFormattedCount}
+          label={tCounter("label")}
+          increment={tCounter("increment")}
+        />
+      </main>
+    </NextIntlClientProvider>
   );
 }
 ```
@@ -575,12 +698,16 @@ export default async function LandingPage({
   <TabItem label="intlayer" value="intlayer">
 
 ```tsx fileName="intlayer.config.ts"
-export default {
+import { type IntlayerConfig, Locales } from "intlayer";
+
+const config: IntlayerConfig = {
   internationalization: {
-    locales: ["en", "fr", "es"],
-    defaultLocale: "en",
+    locales: [Locales.ENGLISH, Locales.FRENCH, Locales.SPANISH],
+    defaultLocale: Locales.ENGLISH,
   },
 };
+
+export default config;
 ```
 
 ```tsx fileName="src/app/[locale]/layout.tsx"
@@ -593,14 +720,16 @@ import {
 
 export const dynamic = "force-static";
 
-const LandingLayout: NextLayoutIntlayer = async ({ children, params }) => {
+const LocaleLayout: NextLayoutIntlayer = async ({ children, params }) => {
   const { locale } = await params;
 
   return (
     <html lang={locale} dir={getHTMLTextDir(locale)}>
-      <IntlayerClientProvider locale={locale}>
-        {children}
-      </IntlayerClientProvider>
+      <body>
+        <IntlayerClientProvider locale={locale}>
+          {children}
+        </IntlayerClientProvider>
+      </body>
     </html>
   );
 };
@@ -652,10 +781,12 @@ Let's take an example of a client component rendering a counter.
 <Tab defaultTab="next-intl" group='techno'>
   <TabItem label="next-i18next" value="next-i18next">
 
-**Translations (must be real JSON in `public/locales/...`)**
+**Translations (one JSON per namespace under `src/locales/...`)**
 
-```json fileName="public/locales/en/about.json"
+```json fileName="src/locales/en/about.json"
 {
+  "title": "About",
+  "description": "About page description",
   "counter": {
     "label": "Counter",
     "increment": "Increment"
@@ -663,8 +794,10 @@ Let's take an example of a client component rendering a counter.
 }
 ```
 
-```json fileName="public/locales/fr/about.json"
+```json fileName="src/locales/fr/about.json"
 {
+  "title": "À propos",
+  "description": "Description de la page À propos",
   "counter": {
     "label": "Compteur",
     "increment": "Incrémenter"
@@ -672,19 +805,18 @@ Let's take an example of a client component rendering a counter.
 }
 ```
 
-**Client component**
+**Client component (loads only the required namespace)**
 
-```tsx fileName="src/components/ClientComponentExample.tsx"
+```tsx fileName="src/components/ClientComponent.tsx"
 "use client";
 
-import React, { useMemo, useState } from "react";
-import { useTranslation } from "next-i18next";
+import React, { useState } from "react";
+import { useTranslation } from "react-i18next";
 
-const ClientComponentExample = () => {
+const ClientComponent = () => {
   const { t, i18n } = useTranslation("about");
   const [count, setCount] = useState(0);
 
-  // next-i18next doesn't expose useNumber; use Intl.NumberFormat
   const numberFormat = new Intl.NumberFormat(i18n.language);
 
   return (
@@ -692,17 +824,19 @@ const ClientComponentExample = () => {
       <p>{numberFormat.format(count)}</p>
       <button
         aria-label={t("counter.label")}
-        onClick={() => setCount((count) => count + 1)}
+        onClick={() => setCount((c) => c + 1)}
       >
         {t("counter.increment")}
       </button>
     </div>
   );
 };
+
+export default ClientComponent;
 ```
 
-> Don't forget to add "about" namespace on the page serverSideTranslations
-> We take here the version of react 19.x.x, but for lower versions, you will need to use useMemo to store the instance of the formatter as it's a heavy function
+> Ensure the page/provider includes only the namespaces you need (e.g. `about`).
+> If you use React < 19, memoize heavy formatters like `Intl.NumberFormat`.
 
   </TabItem>
   <TabItem label="next-intl" value="next-intl">
@@ -827,17 +961,15 @@ We will take the case of a UI component. This component is a server component, a
 <Tab defaultTab="next-intl" group='techno'>
   <TabItem label="next-i18next" value="next-i18next">
 
-```tsx fileName="src/pages/about.tsx"
-import type { GetStaticProps } from "next";
-import { useTranslation } from "next-i18next";
-
+```tsx fileName="src/components/ServerComponent.tsx"
 type ServerComponentProps = {
+  t: (key: string) => string;
+  locale: string;
   count: number;
 };
 
-const ServerComponent = ({ count }: ServerComponentProps) => {
-  const { t, i18n } = useTranslation("about");
-  const formatted = new Intl.NumberFormat(i18n.language).format(count);
+const ServerComponent = ({ t, locale, count }: ServerComponentProps) => {
+  const formatted = new Intl.NumberFormat(locale).format(count);
 
   return (
     <div>
@@ -846,6 +978,8 @@ const ServerComponent = ({ count }: ServerComponentProps) => {
     </div>
   );
 };
+
+export default ServerComponent;
 ```
 
   </TabItem>
@@ -853,20 +987,29 @@ const ServerComponent = ({ count }: ServerComponentProps) => {
 
 ```tsx fileName="src/components/ServerComponent.tsx"
 type ServerComponentProps = {
-  count: number;
   t: (key: string) => string;
+  locale: string;
+  count: number;
+  formatter: Intl.NumberFormat;
 };
 
-const ServerComponent = ({ t, count }: ServerComponentProps) => {
-  const formatted = new Intl.NumberFormat(i18n.language).format(count);
+const ServerComponent = ({
+  t,
+  locale,
+  count,
+  formatter,
+}: ServerComponentProps) => {
+  const formatted = formatter.format(count);
 
   return (
     <div>
       <p>{formatted}</p>
-      <button aria-label={t("label")}>{t("increment")}</button>
+      <button aria-label={t("counter.label")}>{t("counter.increment")}</button>
     </div>
   );
 };
+
+export default ServerComponent;
 ```
 
 > As the server component cannot be async, you need to pass the translations and formatter function as props.
@@ -875,7 +1018,7 @@ const ServerComponent = ({ t, count }: ServerComponentProps) => {
 >
 > - `import { getTranslations, getFormatter } from "next-intl/server";`
 > - `const t = await getTranslations("about.counter");`
-> - `const format = await getFormatter();`
+> - `const formatter = await getFormatter().then((formatter) => formatter.number());`
 
   </TabItem>
   <TabItem label="intlayer" value="intlayer">
@@ -945,17 +1088,20 @@ export function abs(locale: string, path: string) {
 import type { Metadata } from "next";
 import { locales, defaultLocale, localizedPath } from "@/i18n.config";
 
-export async function generateMetadata({
+type GenerateMetadataParams = {
+  params: Promise<{
+    locale: string;
+  }>;
+};
+
+export const generateMetadata = async ({
   params,
-}: {
-  params: { locale: string };
-}): Promise<Metadata> {
-  const { locale } = params;
+}: GenerateMetadataParams): Promise<Metadata> => {
+  const { locale } = await params;
 
-  // Dynamically import the correct JSON file
-  const messages = (
-    await import("@/../public/locales/" + locale + "/about.json")
-  ).default;
+  // Import the correct JSON bundle from src/locales
+  const messages = (await import("@/locales/" + locale + "/about.json"))
+    .default;
 
   const languages = Object.fromEntries(
     locales.map((locale) => [locale, localizedPath(locale, "/about")])
@@ -969,7 +1115,7 @@ export async function generateMetadata({
       languages: { ...languages, "x-default": "/about" },
     },
   };
-}
+};
 
 export default async function AboutPage() {
   return <h1>About</h1>;
@@ -980,7 +1126,7 @@ export default async function AboutPage() {
 import type { MetadataRoute } from "next";
 import { locales, defaultLocale, abs } from "@/i18n.config";
 
-export default function sitemap(): MetadataRoute.Sitemap {
+export const sitemap = (): MetadataRoute.Sitemap => {
   const languages = Object.fromEntries(
     locales.map((locale) => [locale, abs(locale, "/about")])
   );
@@ -993,7 +1139,7 @@ export default function sitemap(): MetadataRoute.Sitemap {
       alternates: { languages },
     },
   ];
-}
+};
 ```
 
 ```ts fileName="src/app/robots.ts"
@@ -1009,7 +1155,7 @@ const expandAllLocales = (path: string) => [
     .map((locale) => localizedPath(locale, path)),
 ];
 
-export default function robots(): MetadataRoute.Robots {
+export const robots = (): MetadataRoute.Robots => {
   const disallow = [
     ...expandAllLocales("/dashboard"),
     ...expandAllLocales("/admin"),
@@ -1020,7 +1166,7 @@ export default function robots(): MetadataRoute.Robots {
     host: ORIGIN,
     sitemap: ORIGIN + "/sitemap.xml",
   };
-}
+};
 ```
 
   </TabItem>
@@ -1031,16 +1177,20 @@ import type { Metadata } from "next";
 import { locales, defaultLocale } from "@/i18n";
 import { getTranslations } from "next-intl/server";
 
-function localizedPath(locale: string, path: string) {
+const localizedPath = (locale: string, path: string) => {
   return locale === defaultLocale ? path : "/" + locale + path;
-}
+};
 
-export async function generateMetadata({
+type GenerateMetadataParams = {
+  params: Promise<{
+    locale: string;
+  }>;
+};
+
+export const generateMetadata = async ({
   params,
-}: {
-  params: { locale: string };
-}): Promise<Metadata> {
-  const { locale } = params;
+}: GenerateMetadataParams): Promise<Metadata> => {
+  const { locale } = await params;
   const t = await getTranslations({ locale, namespace: "about" });
 
   const url = "/about";
@@ -1056,7 +1206,7 @@ export async function generateMetadata({
       languages: { ...languages, "x-default": url },
     },
   };
-}
+};
 
 // ... Rest of the page code
 ```
@@ -1070,7 +1220,7 @@ const origin = "https://example.com";
 const formatterLocalizedPath = (locale: string, path: string) =>
   locale === defaultLocale ? origin + path : origin + "/" + locale + path;
 
-export default function sitemap(): MetadataRoute.Sitemap {
+export const sitemap = (): MetadataRoute.Sitemap => {
   const aboutLanguages = Object.fromEntries(
     locales.map((l) => [l, formatterLocalizedPath(l, "/about")])
   );
@@ -1084,7 +1234,7 @@ export default function sitemap(): MetadataRoute.Sitemap {
       alternates: { languages: aboutLanguages },
     },
   ];
-}
+};
 ```
 
 ```tsx fileName="src/app/robots.ts"
@@ -1099,7 +1249,7 @@ const withAllLocales = (path: string) => [
     .map((locale) => "/" + locale + path),
 ];
 
-export default function robots(): MetadataRoute.Robots {
+export const robots = (): MetadataRoute.Robots => {
   const disallow = [
     ...withAllLocales("/dashboard"),
     ...withAllLocales("/admin"),
@@ -1110,7 +1260,7 @@ export default function robots(): MetadataRoute.Robots {
     host: origin,
     sitemap: origin + "/sitemap.xml",
   };
-}
+};
 ```
 
   </TabItem>
@@ -1181,7 +1331,111 @@ export default robots;
 
 > Intlayer provides a `getMultilingualUrls` function to generate multilingual URLs for your sitemap.
 
----
+### Middleware for locale routing
+
+<Tab defaultTab="next-intl" group='techno'>
+  <TabItem label="next-i18next" value="next-i18next">
+
+Add a middleware to handle locale detection and routing:
+
+```ts fileName="src/middleware.ts"
+import { NextResponse, type NextRequest } from "next/server";
+import { defaultLocale, locales } from "@/i18n.config";
+
+const PUBLIC_FILE = /\.[^/]+$/; // exclude files with extensions
+
+export function middleware(request: NextRequest) {
+  const { pathname } = request.nextUrl;
+
+  if (
+    pathname.startsWith("/_next") ||
+    pathname.startsWith("/api") ||
+    pathname.startsWith("/static") ||
+    PUBLIC_FILE.test(pathname)
+  ) {
+    return;
+  }
+
+  const hasLocale = locales.some(
+    (l) => pathname === "/" + l || pathname.startsWith("/" + l + "/")
+  );
+  if (!hasLocale) {
+    const locale = defaultLocale;
+    const url = request.nextUrl.clone();
+    url.pathname = "/" + locale + (pathname === "/" ? "" : pathname);
+    return NextResponse.redirect(url);
+  }
+}
+
+export const config = {
+  matcher: [
+    // Match all paths except the ones starting with these and files with an extension
+    "/((?!api|_next|static|.*\\..*).*)",
+  ],
+};
+```
+
+  </TabItem>
+  <TabItem label="next-intl" value="next-intl">
+
+Add a middleware to handle locale detection and routing:
+
+```ts fileName="src/middleware.ts"
+import createMiddleware from "next-intl/middleware";
+import { locales, defaultLocale } from "@/i18n";
+
+export default createMiddleware({
+  locales: [...locales],
+  defaultLocale,
+  localeDetection: true,
+});
+
+export const config = {
+  // Skip API, Next internals and static assets
+  matcher: ["/((?!api|_next|.*\\..*).*)"],
+};
+```
+
+  </TabItem>
+  <TabItem label="intlayer" value="intlayer">
+
+Intlayer provides built-in middleware handling through the `next-intlayer` package configuration.
+
+  </TabItem>
+</Tab>
+
+### Setup checklist and good practices
+
+<Tab defaultTab="next-intl" group='techno'>
+  <TabItem label="next-i18next" value="next-i18next">
+
+- Ensure `lang` and `dir` are set on the root `<html>` in `src/app/[locale]/layout.tsx`.
+- Split translations into namespaces (for example `common.json`, `about.json`) under `src/locales/<locale>/`.
+- Only load required namespaces in client components using `useTranslation('<ns>')` and by scoping `I18nProvider` with the same namespaces.
+- Keep pages static when possible: export `export const dynamic = 'force-static'` on pages; set `dynamicParams = false` and implement `generateStaticParams`.
+- Use sync server components nested under client boundaries by passing already-computed strings or the `t` function and the `locale`.
+- For SEO, set `alternates.languages` in metadata, list localized URLs in `sitemap.ts`, and disallow duplicate localized routes in `robots.ts`.
+- Prefer locale-aware formatters (e.g., `Intl.NumberFormat(locale)`) and memoize them on the client if using React < 19.
+
+  </TabItem>
+  <TabItem label="next-intl" value="next-intl">
+
+- **Set html `lang` and `dir`**: In `src/app/[locale]/layout.tsx`, compute `dir` via `getLocaleDirection(locale)` and set `<html lang={locale} dir={dir}>`.
+- **Split messages by namespace**: Organize JSON per locale and namespace (e.g., `common.json`, `about.json`).
+- **Minimize client payload**: On pages, send only required namespaces to `NextIntlClientProvider` (e.g., `pick(messages, ['common', 'about'])`).
+- **Prefer static pages**: Export `export const dynamic = 'force-static'` and generate static params for all `locales`.
+- **Synchronous server components**: Keep server components sync by passing precomputed strings (translated labels, formatted numbers) rather than async calls or non-serializable functions.
+
+  </TabItem>
+  <TabItem label="intlayer" value="intlayer">
+
+- **Modular content**: Co-locate content dictionaries with components using `.content.{ts|js|json}` files.
+- **Type safety**: Leverage TypeScript integration for compile-time content validation.
+- **Build-time optimization**: Use Intlayer's build tools for automatic tree-shaking and bundle optimization.
+- **Integrated tooling**: Take advantage of built-in routing, SEO helpers, and visual editor support.
+
+  </TabItem>
+</Tab>
 
 ---