@intlayer/docs 9.3.2 → 9.4.0-canary.0

package/docs/en/mcp_server.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-06-07
-updatedAt: 2026-03-03
+updatedAt: 2026-08-21
 title: MCP Server Documentation
 description: Explore the features and setup of the MCP Server to optimize your server management and operations.
 keywords:
@@ -15,6 +15,9 @@ slugs:
   - doc
   - mcp-server
 history:
+  - version: 9.3.3
+    date: 2026-08-21
+    changes: "Group the platform setup sections into tabs"
   - version: 5.5.12
     date: 2025-07-11
     changes: "Add set up of ChatGPT"
@@ -113,13 +116,18 @@ This command will:
 
 ---
 
-## Setup in Cursor
+## Manual setup
+
+<Tabs defaultTab="cursor">
+  <Tab label="Cursor" value="cursor">
+
+### Setup in Cursor
 
 Follow the [official documentation](https://docs.cursor.com/context/mcp) to configure the MCP server in Cursor.
 
 In your project root, add the following `.cursor/mcp.json` configuration file:
 
-### Local server (stdio) (recommended)
+#### Local server (stdio) (recommended)
 
 ```json fileName=".cursor/mcp.json"
 {
@@ -132,7 +140,7 @@ In your project root, add the following `.cursor/mcp.json` configuration file:
 }
 ```
 
-### Remote server (Streamable HTTP)
+#### Remote server (Streamable HTTP)
 
 For connecting to a remote Intlayer MCP server using Streamable HTTP, you can configure your MCP client to connect to the hosted service.
 
@@ -149,15 +157,16 @@ For connecting to a remote Intlayer MCP server using Streamable HTTP, you can co
 
 This tells your IDE to launch the Intlayer MCP server using `npx`, ensuring it always uses the latest available version unless you pin it.
 
----
+  </Tab>
+  <Tab label="VS Code" value="vscode">
 
-## Setup in VS Code
+### Setup in VS Code
 
 Follow the [official documentation](https://code.visualstudio.com/docs/copilot/chat/mcp-servers) to configure the MCP server in VS Code.
 
 To use the Intlayer MCP Server with VS Code, you need to configure it in your workspace or user settings.
 
-### Local server (stdio) (recommended)
+#### Local server (stdio) (recommended)
 
 Create a `.vscode/mcp.json` file in your project root:
 
@@ -173,7 +182,7 @@ Create a `.vscode/mcp.json` file in your project root:
 }
 ```
 
-### Remote server (Streamable HTTP)
+#### Remote server (Streamable HTTP)
 
 For connecting to a remote Intlayer MCP server using Streamable HTTP, you can configure your MCP client to connect to the hosted service.
 
@@ -188,11 +197,12 @@ For connecting to a remote Intlayer MCP server using Streamable HTTP, you can co
 }
 ```
 
----
+  </Tab>
+  <Tab label="ChatGPT" value="chatgpt">
 
-## Set Up in ChatGPT
+### Set Up in ChatGPT
 
-### Remote server (Streamable HTTP)
+#### Remote server (Streamable HTTP)
 
 Follow the [official documentation](https://platform.openai.com/docs/mcp#test-and-connect-your-mcp-server) to configure the MCP server in ChatGPT.
 
@@ -209,9 +219,10 @@ Follow the [official documentation](https://platform.openai.com/docs/mcp#test-an
 
 7. Click on `Save`
 
----
+  </Tab>
+  <Tab label="Claude Desktop" value="claude-desktop">
 
-## Set Up in Claude Desktop
+### Set Up in Claude Desktop
 
 Follow the [official documentation](https://modelcontextprotocol.io/quickstart/user#2-add-the-filesystem-mcp-server) to configure the MCP server in Claude Desktop.
 
@@ -220,7 +231,7 @@ Path of the config file:
 - macOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json`
 - Windows: `%APPDATA%\Claude\claude_desktop_config.json`
 
-### Local server (stdio) (recommended)
+#### Local server (stdio) (recommended)
 
 ```json fileName="claude_desktop_config.json"
 {
@@ -233,7 +244,7 @@ Path of the config file:
 }
 ```
 
-### Remote server (Streamable HTTP)
+#### Remote server (Streamable HTTP)
 
 ```json fileName="claude_desktop_config.json"
 {
@@ -246,13 +257,14 @@ Path of the config file:
 }
 ```
 
----
+  </Tab>
+  <Tab label="Claude Code (CLI)" value="claude-code">
 
-## Set Up in Claude Code (CLI)
+### Set Up in Claude Code (CLI)
 
 Follow the [official documentation](https://modelcontextprotocol.io/quickstart/user) to configure the MCP server in Claude Code.
 
-### Local server (stdio) (recommended)
+#### Local server (stdio) (recommended)
 
 To connect the Intlayer MCP server to Claude Code using stdio:
 
@@ -260,7 +272,7 @@ To connect the Intlayer MCP server to Claude Code using stdio:
 claude mcp add intlayer npx -y @intlayer/mcp
 ```
 
-### Remote server (Streamable HTTP)
+#### Remote server (Streamable HTTP)
 
 To connect the Intlayer MCP server to Claude Code using Streamable HTTP (SSE):
 
@@ -268,6 +280,9 @@ To connect the Intlayer MCP server to Claude Code using Streamable HTTP (SSE):
 claude mcp add intlayer https://mcp.intlayer.org -t http
 ```
 
+  </Tab>
+</Tabs>
+
 ---
 
 ## Using the MCP Server via CLI

package/docs/en/packages/intlayer/getLocalizedPath.md

@@ -19,6 +19,9 @@ slugs:
   - intlayer
   - getLocalizedPath
 history:
+  - version: 8.0.0
+    date: 2026-08-19
+    changes: "Apply the locale prefix, and narrow the return type from the declared rewrite rules"
   - version: 8.0.0
     date: 2026-01-22
     changes: "Implement custom URL rewrites"
@@ -29,13 +32,17 @@ author: aymericzip
 
 ## Description
 
-The `getLocalizedPath` function resolves a canonical path (internal application path) into its localized equivalent based on the provided locale and rewrite rules. It is particularly useful for generating SEO-friendly URLs that vary by language.
+The `getLocalizedPath` function localizes a canonical path (internal application path): it resolves the custom rewrite rules, then applies the locale prefix of your routing mode. It is particularly useful for generating SEO-friendly URLs that vary by language.
+
+It is the relative counterpart of [`getLocalizedUrl`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getLocalizedUrl.md) — for a relative input both return the same value. Unlike `getLocalizedUrl`, it never returns an absolute URL: the `domains` configuration is ignored, so a locale served from its own domain still yields a path. An absolute input is accepted, but its origin is dropped — only its path, query string and hash are kept.
 
 **Key Features:**
 
 - Supports dynamic route parameters using the `[param]` syntax.
 - Resolves paths according to custom rewrite rules defined in your configuration.
+- Applies the locale prefix of the configured routing mode (`prefix-no-default`, `prefix-all`, …).
 - Automatically handles fallback to the canonical path if no rewrite rule is found for the specified locale.
+- Narrows its return type: a literal path resolves to the localized string literal at compile time.
 
 ---
 
@@ -43,9 +50,14 @@ The `getLocalizedPath` function resolves a canonical path (internal application
 
 ```typescript
 getLocalizedPath(
-  canonicalPath: string,         // Required
-  locale: Locales,               // Required
-  rewriteRules?: RoutingConfig['rewrite'] // Optional
+  canonicalPath: string,     // Required
+  locale?: Locales,          // Optional
+  options?: {                // Optional
+    locales?: Locales[];
+    defaultLocale?: Locales;
+    mode?: 'prefix-no-default' | 'prefix-all' | 'no-prefix' | 'search-params';
+    rewrite?: RoutingConfig['rewrite'];
+  }
 ): string
 ```
 
@@ -60,17 +72,21 @@ getLocalizedPath(
   - **Type**: `string`
   - **Required**: Yes
 
-- `locale: Locales`
+### Optional Parameters
+
+- `locale?: Locales`
   - **Description**: The target locale for which the path should be localized.
   - **Type**: `Locales`
-  - **Required**: Yes
+  - **Default**: The default locale of your project's configuration.
 
-### Optional Parameters
+- `options?: object`
+  - **Description**: Routing overrides. Every entry defaults to your project's configuration.
+  - **Type**: `object`
 
-- `rewriteRules?: RoutingConfig['rewrite']`
-  - **Description**: An object defining custom rewrite rules. If not provided, it defaults to the `routing.rewrite` property from your project's configuration.
-  - **Type**: `RoutingConfig['rewrite']`
-  - **Default**: `configuration.routing.rewrite`
+  - `options.locales?: Locales[]` — supported locales. **Default**: `configuration.internationalization.locales`
+  - `options.defaultLocale?: Locales` — the default locale. **Default**: `configuration.internationalization.defaultLocale`
+  - `options.mode?: 'prefix-no-default' | 'prefix-all' | 'no-prefix' | 'search-params'` — how the locale appears in the path. **Default**: `configuration.routing.mode`
+  - `options.rewrite?: RoutingConfig['rewrite']` — custom rewrite rules. **Default**: `configuration.routing.rewrite`
 
 ---
 
@@ -79,6 +95,28 @@ getLocalizedPath(
 - **Type**: `string`
 - **Description**: The localized path for the specified locale.
 
+The type is narrowed from the rewrite rules declared in your configuration, so the editor shows the resolved path rather than a bare `string`:
+
+```typescript codeFormat="typescript"
+// Configuration: mode 'prefix-no-default', defaultLocale 'en',
+//                { '/about': { fr: '/a-propos' }, '/product/[id]': { fr: '/produit/[id]' } }
+const about = getLocalizedPath("/about", Locales.FRENCH);
+//    ^? '/fr/a-propos'
+const product = getLocalizedPath("/product/123", Locales.FRENCH);
+//    ^? '/fr/produit/123'
+const contact = getLocalizedPath("/contact", Locales.FRENCH);
+//    ^? '/fr/contact'  (no rewrite rule matches, only the prefix is applied)
+const home = getLocalizedPath("/", Locales.FRENCH);
+//    ^? '/fr'
+```
+
+The same narrowing flows into [`getLocalizedUrl`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getLocalizedUrl.md), which applies the rewrite rules before prefixing the locale.
+
+Two cases stay widened to `string`, because they cannot be resolved at compile time:
+
+- a path that is not a string literal (e.g. one built from a variable);
+- a path matched by a rule using a multi-segment or optional parameter (`[...slug]`, `[[...slug]]`, `:param?`).
+
 ---
 
 ## Example Usage
@@ -90,12 +128,13 @@ If you have configured custom rewrites in your `intlayer.config.ts`:
 ```typescript codeFormat="typescript"
 import { getLocalizedPath, Locales } from "intlayer";
 
-// Configuration: { '/about': { en: '/about', fr: '/a-propos' } }
+// Configuration: mode 'prefix-no-default', defaultLocale 'en',
+//                { '/about': { en: '/about', fr: '/a-propos' } }
 getLocalizedPath("/about", Locales.FRENCH);
-// Output: "/a-propos"
+// Output: "/fr/a-propos"
 
 getLocalizedPath("/about", Locales.ENGLISH);
-// Output: "/about"
+// Output: "/about" (default locale, no prefix)
 ```
 
 ### Usage with Dynamic Routes
@@ -105,7 +144,7 @@ import { getLocalizedPath, Locales } from "intlayer";
 
 // Configuration: { '/product/[id]': { en: '/product/[id]', fr: '/produit/[id]' } }
 getLocalizedPath("/product/123", Locales.FRENCH);
-// Output: "/produit/123"
+// Output: "/fr/produit/123"
 ```
 
 ### Manual Rewrite Rules
@@ -122,13 +161,25 @@ const manualRules = {
   },
 };
 
-getLocalizedPath("/contact", Locales.FRENCH, manualRules);
-// Output: "/contactez-nous"
+getLocalizedPath("/contact", Locales.FRENCH, { rewrite: manualRules });
+// Output: "/fr/contactez-nous"
+```
+
+### Omitting the Locale
+
+When no locale is given, the path is localized for the configured default locale:
+
+```typescript codeFormat="typescript"
+import { getLocalizedPath } from "intlayer";
+
+// Configuration: defaultLocale = Locales.ENGLISH, { '/about': { en: '/about', fr: '/a-propos' } }
+getLocalizedPath("/about");
+// Output: "/about"
 ```
 
 ---
 
 ## Related Functions
 
-- [`getCanonicalPath`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getCanonicalPath.md): Resolves a localized path back to its internal canonical path.
-- [`getLocalizedUrl`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getLocalizedUrl.md): Generates a fully localized URL (including protocol, host, and locale prefix).
+- [`getCanonicalPath`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getCanonicalPath.md): Resolves a localized path back to its internal canonical path. Note that it undoes the rewrite rules only — strip the locale prefix with [`getPathWithoutLocale`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getPathWithoutLocale.md) first.
+- [`getLocalizedUrl`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getLocalizedUrl.md): Same localization, but able to return an absolute URL (protocol, host, domain routing).

package/docs/en/packages/next-intlayer/exports.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2026-01-21
-updatedAt: 2026-01-21
+updatedAt: 2026-08-22
 title: next-intlayer Package Documentation
 description: Next.js-specific integration for Intlayer, providing middleware and providers for App Router and Page Router.
 keywords:
@@ -15,6 +15,9 @@ slugs:
   - next-intlayer
   - exports
 history:
+  - version: 9.4.0
+    date: 2026-08-22
+    changes: "Update to Next.js >= 9.4.0 architecture"
   - version: 10.0.0
     date: 2026-06-23
     changes: "Add usePathname utility"
@@ -75,15 +78,15 @@ or
 import "next-intlayer/server";
 ```
 
-| Component                | Description                                                                                                  | Related Doc |
-| ------------------------ | ------------------------------------------------------------------------------------------------------------ | ----------- |
-| `IntlayerClientProvider` | Provider for client-side components in Next.js App Router. Wraps `IntlayerProvider` from react-intlayer.     | -           |
-| `IntlayerServerProvider` | Provider for server-side components in Next.js (App Router). Provides locale context on the server.          | -           |
-| `IntlayerServer`         | Server-side wrapper for Intlayer content in App Router. Ensures proper locale handling in Server Components. | -           |
-| `HTMLProvider`           | Provider for HTML-related internationalization settings. Allows component overrides for HTML tags.           | -           |
-| `HTMLRenderer`           | Renders HTML content with custom components.                                                                 | -           |
-| `MarkdownProvider`       | Provider for markdown rendering context. Allows custom component overrides for markdown elements.            | -           |
-| `MarkdownRenderer`       | Renders markdown content with custom components.                                                             | -           |
+| Component                | Description                                                                                                          | Related Doc |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------- | ----------- |
+| `IntlayerClientProvider` | Provider for client-side components in Next.js App Router. Wraps `IntlayerProvider` from react-intlayer.             | -           |
+| `IntlayerServerProvider` | Provider for server-side components in Next.js (App Router). Provides locale context on the server. (Intlayer < 9.4) | -           |
+| `IntlayerServer`         | Server-side wrapper for Intlayer content in App Router. Ensures proper locale handling in Server Components.         | -           |
+| `HTMLProvider`           | Provider for HTML-related internationalization settings. Allows component overrides for HTML tags.                   | -           |
+| `HTMLRenderer`           | Renders HTML content with custom components.                                                                         | -           |
+| `MarkdownProvider`       | Provider for markdown rendering context. Allows custom component overrides for markdown elements.                    | -           |
+| `MarkdownRenderer`       | Renders markdown content with custom components.                                                                     | -           |
 
 ### Hooks (Client-side)
 

package/docs/en/packages/next-intlayer/t.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-08-23
-updatedAt: 2025-08-23
+updatedAt: 2026-08-22
 title: t Function Documentation | next-intlayer
 description: See how to use the t function for next-intlayer package
 keywords:
@@ -19,6 +19,9 @@ slugs:
   - next-intlayer
   - t
 history:
+  - version: 9.4.0
+    date: 2026-08-22
+    changes: "Update to Next.js >= 9.4.0 architecture"
   - version: 5.5.10
     date: 2025-06-29
     changes: "Init history"
@@ -154,25 +157,48 @@ const greeting = t(translations);
 
 ### Locale Detection and Context
 
-In `next-intlayer`, the current locale is managed through context providers: `IntlayerClientProvider` and `IntlayerServerProvider`. Ensure these providers wrap your components and the `locale` prop is correctly passed.
+In `next-intlayer`, the current locale is managed through context providers: `IntlayerClientProvider` and `IntlayerServerProvider` (or just `IntlayerProvider` for Intlayer >= 9.4). Ensure these providers wrap your components and the `locale` prop is correctly passed.
 
 #### Example:
 
+<Tabs>
+ <Tab label='Intlayer >=9.4' value='>=9.4'>
+
 ```tsx codeFormat={["typescript", "esm", "commonjs"]}
-import type { FC } from "react";
+import type { FC, ReactNode } from "react";
+import type { Locales } from "intlayer";
+import { IntlayerClientProvider } from "next-intlayer";
+
+const Page: FC<{ locale: Locales; children: ReactNode }> = ({
+  locale,
+  children,
+}) => (
+  <IntlayerClientProvider locale={locale}>{children}</IntlayerClientProvider>
+);
+```
+
+ </Tab>
+ <Tab label='Intlayer <9.4' value='<9.4'>
+
+```tsx codeFormat={["typescript", "esm", "commonjs"]}
+import type { FC, ReactNode } from "react";
 import type { Locales } from "intlayer";
 import { IntlayerClientProvider } from "next-intlayer";
 import { IntlayerServerProvider } from "next-intlayer/server";
 
-const Page: FC<{ locale: Locales }> = ({ locale }) => (
+const Page: FC<{ locale: Locales; children: ReactNode }> = ({
+  locale,
+  children,
+}) => (
   <IntlayerServerProvider locale={locale}>
-    <IntlayerClientProvider locale={locale}>
-      {/* Your components here */}
-    </IntlayerClientProvider>
+    <IntlayerClientProvider locale={locale}>{children}</IntlayerClientProvider>
   </IntlayerServerProvider>
 );
 ```
 
+ </Tab>
+</Tabs>
+
 ---
 
 ## Common Errors and Troubleshooting
@@ -181,7 +207,7 @@ const Page: FC<{ locale: Locales }> = ({ locale }) => (
 
 - **Cause**: The current locale is not properly set, or the translation for the current locale is missing.
 - **Solution**:
-  - Verify that the `IntlayerClientProvider` or `IntlayerServerProvider` is correctly set up with the appropriate `locale`.
+  - Verify that the `IntlayerProvider` (or `IntlayerClientProvider`/`IntlayerServerProvider`) is correctly set up with the appropriate `locale`.
   - Ensure that your translations object includes all the necessary locales.
 
 ### Missing Translations in TypeScript
@@ -218,4 +244,4 @@ For more detailed usage and advanced features, refer to the [next-intlayer docum
 
 ---
 
-**Note**: Remember to set up your `IntlayerClientProvider` and `IntlayerServerProvider` properly to ensure that the current locale is correctly passed down to your components. This is crucial for the `t` function to return the correct translations.
+**Note**: Remember to set up your `IntlayerProvider` (or `IntlayerClientProvider` and `IntlayerServerProvider`) properly to ensure that the current locale is correctly passed down to your components. This is crucial for the `t` function to return the correct translations.

package/docs/en/packages/next-intlayer/useDictionary.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-08-23
-updatedAt: 2025-08-23
+updatedAt: 2026-08-22
 title: useDictionary Hook Documentation | next-intlayer
 description: See how to use the useDictionary hook for next-intlayer package
 keywords:
@@ -19,6 +19,9 @@ slugs:
   - next-intlayer
   - useDictionary
 history:
+  - version: 9.4.0
+    date: 2026-08-22
+    changes: "Update to Next.js >= 9.4.0 architecture"
   - version: 5.5.10
     date: 2025-06-29
     changes: "Init history"
@@ -119,7 +122,7 @@ const ClientComponentExample: FC = () => {
 
 ## Example Usage in React Server Component
 
-If you're using the `useDictionary` hook outside the `IntlayerServerProvider`, the locale must be explicitly provided as a parameter when rendering the component:
+If you're using the `useDictionary` hook outside the `IntlayerProvider` (or `IntlayerServerProvider` for Intlayer < 9.4), the locale must be explicitly provided as a parameter when rendering the component:
 
 ```tsx fileName="ServerComponentExample.tsx" codeFormat={["typescript", "esm"]}
 import type { FC } from "react";

package/docs/en/packages/next-intlayer/useIntlayer.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-08-23
-updatedAt: 2026-05-06
+updatedAt: 2026-08-22
 title: useIntlayer Hook Documentation | next-intlayer
 description: See how to use the useIntlayer hook for next-intlayer package
 keywords:
@@ -19,6 +19,9 @@ slugs:
   - next-intlayer
   - useIntlayer
 history:
+  - version: 9.4.0
+    date: 2026-08-22
+    changes: "Update to Next.js >= 9.4.0 architecture"
   - version: 8.9.0
     date: 2026-05-04
     changes: "Update Solid useIntlayer API usage to direct property access"
@@ -79,6 +82,35 @@ Instructions for setting up content declaration files are available [here](https
 
 Here's how you can implement the `useIntlayer` hook within a Next.js page to dynamically load localized content based on the application's current locale:
 
+<Tabs>
+ <Tab label='Intlayer >=9.4' value='>=9.4'>
+
+```tsx fileName="src/pages/[locale]/index.tsx" codeFormat={["typescript", "esm"]}
+import { ClientComponentExample } from "@components/ClientComponentExample";
+import { ServerComponentExample } from "@components/ServerComponentExample";
+import { type NextPageIntlayer, IntlayerClientProvider } from "next-intlayer";
+import { useIntlayer } from "next-intlayer";
+
+const HomePage: NextPageIntlayer = async ({ params }) => {
+  const { locale } = await params;
+
+  const content = useIntlayer("homepage", locale);
+
+  return (
+    <>
+      <p>{content.introduction}</p>
+      <IntlayerClientProvider locale={locale}>
+        <ClientComponentExample />
+      </IntlayerClientProvider>
+      <ServerComponentExample />
+    </>
+  );
+};
+```
+
+ </Tab>
+ <Tab label='Intlayer <9.4' value='<9.4'>
+
 ```tsx fileName="src/pages/[locale]/index.tsx" codeFormat={["typescript", "esm"]}
 import { ClientComponentExample } from "@components/ClientComponentExample";
 import { ServerComponentExample } from "@components/ServerComponentExample";
@@ -104,6 +136,9 @@ const HomePage: NextPageIntlayer = async ({ params }) => {
 };
 ```
 
+ </Tab>
+</Tabs>
+
 ```tsx fileName="src/components/ClientComponentExample.tsx" codeFormat={["typescript", "esm"]}
 "use-client";
 

package/docs/en/packages/react-intlayer/exports.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2026-01-21
-updatedAt: 2026-01-21
+updatedAt: 2026-08-22
 title: react-intlayer Package Documentation
 description: React-specific implementation of Intlayer, providing hooks and providers for React applications.
 keywords:
@@ -14,6 +14,9 @@ slugs:
   - react-intlayer
   - exports
 history:
+  - version: 9.4.0
+    date: 2026-08-22
+    changes: "Update to Next.js >= 9.4.0 architecture"
   - version: 10.0.0
     date: 2026-06-23
     changes: "Add usePathname utility"
@@ -137,13 +140,13 @@ Import:
 import "react-intlayer/server";
 ```
 
-| Export                   | Type        | Description                                      |
-| ------------------------ | ----------- | ------------------------------------------------ |
-| `IntlayerServerProvider` | `Component` | Provider for server-side rendering.              |
-| `IntlayerServer`         | `Component` | Server-side wrapper for Intlayer content.        |
-| `t`                      | `Function`  | Server-side version of the translation function. |
-| `useLocale`              | `Hook`      | Hook to access locale on the server side.        |
-| `useIntlayer`            | `Hook`      | Server-side version of `useIntlayer`.            |
-| `useDictionary`          | `Hook`      | Server-side version of `useDictionary`.          |
-| `useI18n`                | `Hook`      | Server-side version of `useI18n`.                |
-| `locale`                 | `Function`  | Function to get or set the locale on the server. |
+| Export                   | Type        | Description                                          |
+| ------------------------ | ----------- | ---------------------------------------------------- |
+| `IntlayerServerProvider` | `Component` | Provider for server-side rendering. (Intlayer < 9.4) |
+| `IntlayerServer`         | `Component` | Server-side wrapper for Intlayer content.            |
+| `t`                      | `Function`  | Server-side version of the translation function.     |
+| `useLocale`              | `Hook`      | Hook to access locale on the server side.            |
+| `useIntlayer`            | `Hook`      | Server-side version of `useIntlayer`.                |
+| `useDictionary`          | `Hook`      | Server-side version of `useDictionary`.              |
+| `useI18n`                | `Hook`      | Server-side version of `useI18n`.                    |
+| `locale`                 | `Function`  | Function to get or set the locale on the server.     |

package/docs/en/packages/react-intlayer/useI18n.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-08-23
-updatedAt: 2025-08-23
+updatedAt: 2026-08-22
 title: useI18n Hook Documentation | react-intlayer
 description: Learn how to use the useI18n hook in the react-intlayer package
 keywords:
@@ -20,6 +20,9 @@ slugs:
   - react-intlayer
   - useI18n
 history:
+  - version: 9.4.0
+    date: 2026-08-22
+    changes: "Update to Next.js >= 9.4.0 architecture"
   - version: 6.0.0
     date: 2025-06-29
     changes: "Initial writing of `useI18n` hook documentation"
@@ -77,6 +80,34 @@ All dictionary keys must be declared within content declaration files to enhance
 
 Examples of using the `useI18n` hook within React components:
 
+<Tabs>
+ <Tab label='Intlayer >=9.4' value='>=9.4'>
+
+```tsx fileName="src/App.tsx" codeFormat={["typescript", "esm"]}
+import type { FC } from "react";
+import { ClientComponentExample, ServerComponentExample } from "@components";
+import { IntlayerProvider } from "react-intlayer";
+import { useI18n } from "react-intlayer/server";
+import { Locales } from "intlayer";
+
+const App: FC<{ locale: Locales }> = ({ locale }) => {
+  const t = useI18n("home-page", locale);
+
+  return (
+    <>
+      <p>{t("introduction")}</p>
+      <IntlayerProvider locale={locale}>
+        <ClientComponentExample />
+      </IntlayerProvider>
+      <ServerComponentExample />
+    </>
+  );
+};
+```
+
+ </Tab>
+ <Tab label='Intlayer <9.4' value='<9.4'>
+
 ```tsx fileName="src/App.tsx" codeFormat={["typescript", "esm"]}
 import type { FC } from "react";
 import { ClientComponentExample, ServerComponentExample } from "@components";
@@ -101,6 +132,9 @@ const App: FC<{ locale: Locales }> = ({ locale }) => {
 };
 ```
 
+ </Tab>
+</Tabs>
+
 ```tsx fileName="src/components/ComponentExample.tsx" codeFormat={["typescript", "esm"]}
 import type { FC } from "react";
 import { useI18n } from "react-intlayer";

package/docs/en/packages/vite-intlayer/intlayerMinify.md

@@ -56,7 +56,7 @@ export default defineConfig({
 2. `build.optimize` is `true` (or `undefined`, which defaults to `true` for builds).
 3. `build.minify` is `true` in your Intlayer config.
 
-It is automatically **disabled** when `editor.enabled` is `true` because the editor needs the full, human-readable dictionary content.
+When `editor.enabled` is `true`, the plugin still runs but **skips field renaming**: renaming rewrites the content keys the interpreter walks, so the `keyPath` the visual editor receives would no longer match the unmerged dictionaries it edits. Whitespace compaction and the top-level metadata strip stay active.
 
 ## What gets minified
 

package/docs/en/packages/vite-intlayer/intlayerPrune.md

@@ -120,4 +120,4 @@ When pruning succeeds, `intlayerPrune` also writes `pruneContext.dictionaryKeyTo
 2. `build.optimize` is `true` (or `undefined`, which defaults to `true` for builds).
 3. `build.purge` is `true` in your Intlayer config.
 
-It is automatically **disabled** when `editor.enabled` is `true` because the editor needs the full dictionary content.
+It stays active when `editor.enabled` is `true`: the visual editor resolves every edit through `dictionaryKey` + `keyPath` against the unmerged dictionaries, which this plugin never touches, and a purged field is one no component reads — so it is never rendered and never selectable in the page.