@intlayer/docs 9.0.0-canary.3 → 9.0.0-canary.5

package/docs/de/releases/v7.md

@@ -25,6 +25,10 @@ author: aymericzip
 
 Willkommen bei Intlayer v7! Dieses große Release bringt bedeutende Verbesserungen in Leistung, Typsicherheit und Entwicklererfahrung. Nachfolgend finden Sie die Highlights, Migrationshinweise und praktische Beispiele.
 
+## Inhaltsverzeichnis
+
+<TOC levels={[2]} maxDepth={1} />
+
 ## Highlights
 
 - Caching-Strategie für schnellere Builds
@@ -260,6 +264,126 @@ Dies führt zu schnelleren Downloadzeiten und verbesserter Laufzeitleistung Ihre
 
 ---
 
+## Automatische Code-Formatierung: formatCommand-Konfiguration
+
+v7 führt die `formatCommand`-Option in der Editor-Konfiguration ein, die es Ihnen ermöglicht, Inhaltsdateien automatisch zu formatieren, wenn sie von Intlayer geschrieben werden. Dies gewährleistet einen konsistenten Code-Stil und eine konsistente Formatierung in Ihren Content-Deklarationsdateien.
+
+Falls nicht gesetzt, versucht Intlayer, den Format-Befehl automatisch zu erkennen. Durch den Versuch, die folgenden Befehle aufzulösen: prettier, biome, eslint.
+
+### Konfiguration
+
+Die `formatCommand`-Option akzeptiert eine String-Vorlage, wobei `{{file}}` durch den tatsächlichen Dateipfad ersetzt wird:
+
+```typescript fileName="intlayer.config.ts"
+export default {
+  content: {
+    formatCommand: 'bun x biome format "{{file}}" --write --log-level none',
+  },
+};
+```
+
+### Unterstützte Formatter
+
+Sie können jeden Code-Formatter verwenden, der Dateipfade als Argumente akzeptiert:
+
+**Using Biome:**
+
+```typescript
+formatCommand: 'bun x biome format "{{file}}" --write --log-level none';
+```
+
+**Using Prettier:**
+
+```typescript
+formatCommand: 'npx prettier --write "{{file}}" --log-level silent';
+```
+
+**Using ESLint:**
+
+```typescript
+formatCommand: 'npx eslint --fix "{{file}}" --quiet';
+```
+
+**Using Bun's built-in formatter:**
+
+```typescript
+formatCommand: 'bun format "{{file}}"';
+```
+
+### Vorteile
+
+- **Konsistente Formatierung**: Alle Inhaltsdateien werden automatisch gemäß den Stilrichtlinien Ihres Projekts formatiert
+- **Developer Experience**: Keine manuelle Formatierung von Dateien nach dem Schreiben durch Intlayer erforderlich
+- **Team-Konsistenz**: Stellt sicher, dass alle Teammitglieder die gleiche Formatierung auf Inhaltsdateien anwenden
+- **CI/CD-Integration**: Inhaltsdateien behalten konsistente Formatierung in automatisierten Workflows bei
+
+### Funktionsweise
+
+Wenn Intlayer eine Content-Deklarationsdatei (`.content.ts`, `.content.js`, etc.) schreibt oder aktualisiert, führt es automatisch den angegebenen Format-Befehl auf der Datei aus. Der Platzhalter `{{file}}` wird durch den tatsächlichen Dateipfad ersetzt, und der Befehl wird im Basisverzeichnis des Projekts ausgeführt.
+
+---
+
+## Dictionary-Konfiguration: Bessere Organisation und Struktur
+
+v7 führt einen neuen dedizierten `dictionary`-Konfigurationsbereich ein, der eine bessere Organisation für wörterbuchbezogene Einstellungen und verbessertes Content-Management bietet.
+
+### Neue Dictionary-Konfigurationsstruktur
+
+Die `fill`-Eigenschaft wurde aus dem `content`-Abschnitt in einen neuen `dictionary`-Abschnitt verschoben, was eine klarere Trennung der Verantwortlichkeiten ermöglicht:
+
+**v6-Konfiguration:**
+
+```typescript fileName="intlayer.config.ts"
+export default {
+  content: {
+    autoFill: "./{{fileName}}.content.json",
+    contentDir: ["src"],
+  },
+};
+```
+
+**v7-Konfiguration:**
+
+```typescript fileName="intlayer.config.ts"
+export default {
+  content: {
+    contentDir: ["src"],
+  },
+  dictionary: {
+    fill: "./{{fileName}}.content.json",
+  },
+};
+```
+
+### Vorteile der neuen Struktur
+
+- **Klarere Organisation**: Dictionary-spezifische Einstellungen sind nun zusammengefasst
+- **Bessere Separation of Concerns**: Content Discovery vs. Dictionary-Operationen sind klar getrennt
+- **Verbesserte Wartbarkeit**: Einfacher zu verstehen und zu modifizieren Dictionary-bezogene Konfigurationen
+- **Zukünftige Erweiterbarkeit**: Der Dictionary-Bereich kann zusätzliche Dictionary-spezifische Einstellungen aufnehmen
+- **Umfassendes Dictionary-Management**: Umfasst Eigenschaften wie `title`, `live`, `priority`, `tags`, `version` und `description` zum Erstellen und Verwalten neuer Dictionaries
+
+### Konfigurationsverwendung
+
+Die Wörterbuchkonfiguration dient zwei Hauptzwecken:
+
+1. **Standardwerte**: Definieren Sie Standardwerte beim Erstellen von Content-Deklarationsdateien
+2. **Fallback-Verhalten**: Stellen Sie Fallback-Werte bereit, wenn bestimmte Felder nicht definiert sind, sodass Sie das Wörterbuch-Betriebsverhalten global definieren können
+
+Der Wörterbuchbereich umfasst umfassende Eigenschaften zur Wörterbuchverwaltung:
+
+- **`fill`**: Auto-Fill-Verhalten für die Content-Generierung
+- **`title`**: Standardtitel für neue Wörterbücher
+- **`live`**: Live-Sync-Konfiguration für Echtzeit-Updates
+- **`priority`**: Prioritätseinstellungen für die Wörterbuchauflösung
+- **`tags`**: Standard-Tags für die Content-Organisation
+- **`version`**: Versionsverwaltung für Wörterbuch-Updates
+- **`description`**: Standardbeschreibung für neue Inhalte
+
+Weitere Informationen zu Content-Deklarationsdateien und wie Konfigurationswerte angewendet werden, finden Sie in der [Content-Datei-Dokumentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/de/dictionary/content_file.md).
+
+---
+
 ## Fill-Befehl: Aktualisiertes Verhalten für besseres Content-Management
 
 v7 führt ein verbessertes Verhalten für den `fill`-Befehl ein, das ein vorhersehbareres und flexibleres Content-Management ermöglicht:
@@ -407,6 +531,10 @@ Das System führt automatisch aus:
 - **`middleware.prefixDefault`**: Ersetzt durch `routing.mode`
 - **`middleware.noPrefix`**: Ersetzt durch `routing.mode`
 
+### Neue Konfigurationen
+
+- **`editor.formatCommand`**: Neue Option für automatische Code-Formatierung von Content-Dateien
+
 ### Migrationszuordnung
 
 #### Konfigurationszuordnung

package/docs/de/releases/v9.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2026-06-14
-updatedAt: 2026-06-14
+updatedAt: 2026-06-23
 title: Neues Intlayer v9 – Was ist neu?
 description: Entdecken Sie die Neuerungen in Intlayer v9. Einführung von Drop-in-Kompatibilitätspaketen für beliebte i18n-Bibliotheken und Unterstützung für Collections, Variants und Dynamic Records.
 keywords:
@@ -216,6 +216,42 @@ Zur Build-Zeit scannen `@intlayer/swc` und `@intlayer/babel` Ihre Dateien und er
 
 ---
 
+## Vite Plugin: Bundled Compiler & Proxy
+
+Das `intlayer()` Vite Plugin bündelt nun den **Compiler** und den **Locale-Routing Proxy** direkt, sodass die meisten Projekte nur ein einzelnes Plugin in `vite.config.ts` benötigen:
+
+```ts fileName="vite.config.ts"
+import { defineConfig } from "vite";
+import { intlayer } from "vite-intlayer";
+
+export default defineConfig({
+  plugins: [intlayer()],
+});
+```
+
+- **Compiler**: Aktiviert sich automatisch, wenn `compiler.enabled` gesetzt ist und ein `compiler.output` Pfad konfiguriert ist. Sie müssen `intlayerCompiler()` nicht mehr separat registrieren.
+- **Proxy**: Aktiviert sich automatisch basierend auf der neuen `routing.enableProxy` Option (`true` standardmäßig). Es verbindet die Locale-Erkennung / Umleitung / Rewrite Middleware in Entwicklung, Preview und Production SSR. Sie müssen `intlayerProxy()` nicht mehr separat registrieren.
+
+### `routing.enableProxy` Option
+
+Eine neue `routing.enableProxy` Option kontrolliert, ob der Locale-Routing-Proxy eingebunden ist. Sie ist standardmäßig auf `true` gesetzt. Deaktivieren Sie sie, wenn Sie das Locale-Routing selbst handhaben möchten:
+
+```ts fileName="intlayer.config.ts"
+import type { IntlayerConfig } from "intlayer";
+
+const config: IntlayerConfig = {
+  routing: {
+    enableProxy: false, // Standard: true
+  },
+};
+
+export default config;
+```
+
+Die eigenständigen `intlayerCompiler()` und `intlayerProxy()` Plugins bleiben für erweiterte Setups exportiert. Die Registrierung neben `intlayer()` ist sicher — jedes Plugin dedupliziert sich selbst und läuft nur einmal.
+
+---
+
 ## Migrationshinweise von v8
 
 Wenn Sie von v8 upgraden, beachten Sie, dass v9 keine Breaking Changes enthält. Hier sind jedoch die wichtigsten Änderungen:

package/docs/de/roadmap.md

@@ -29,6 +29,12 @@ Intlayer ist eine Content-Management- und Internationalisierungslösung, die dar
 
 ---
 
+## Inhaltsverzeichnis
+
+<TOC/>
+
+---
+
 ## Aktuelle Funktionen
 
 ### 1. Inhaltsdeklaration
@@ -319,22 +325,6 @@ Intlayer unterstützt **TypeScript** (auch JavaScript) und **JSON** zur Deklarat
 
 ### 4. SEO-Verbesserungen
 
-- Werkzeuge zur **Analyse von Schlüsselwörtern**, der Suchintention der Nutzer und aufkommenden Trends.
-- Vorschläge für verbesserten Inhalt zur besseren Platzierung und zur Verfolgung der langfristigen Leistung.
-
-### 5. Kompatibilität mit weiteren Frameworks
-
-- Es wird daran gearbeitet, **Solid, Svelte, Angular** und weitere zu unterstützen.
-- Ziel ist es, Intlayer mit **jeder JavaScript-basierten Anwendung** kompatibel zu machen.
-
----
-
-## Fazit
-
-- Das System würde im Hintergrund Übersetzungen generieren und Sie dann zur Validierung oder Bearbeitung auffordern.
-
-### 4. SEO-Verbesserungen
-
 - Werkzeuge zur **Analyse von Schlüsselwörtern**, der Suchintention der Nutzer und aufkommenden Trends.
 - Vorschläge für verbesserten Inhalt zur besseren Platzierung und Verfolgung der langfristigen Leistung.
 

package/docs/en/bundle_optimization.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-11-25
-updatedAt: 2026-06-07
+updatedAt: 2026-06-24
 title: Optimizing i18n Bundle Size & Performance
 description: Reduce application bundle size by optimizing internationalization (i18n) content. Learn how to leverage tree shaking and lazy loading for dictionaries with Intlayer.
 keywords:
@@ -16,6 +16,9 @@ slugs:
   - concept
   - bundle-optimization
 history:
+  - version: 8.12.0
+    date: 2026-06-24
+    changes: "List Babel plugins in required pipeline order (extract → purge → minify → optimize) in the reference tables"
   - version: 8.12.0
     date: 2026-06-07
     changes: "Add `intlayerPurgeBabelPlugin` and `intlayerMinifyBabelPlugin` for Babel/Webpack; clarify plugin pipeline"
@@ -191,12 +194,14 @@ Intlayer's build optimization is split across several discrete plugins, each wit
 
 These are used directly in `babel.config.js` for Webpack-based setups (Next.js with Babel, CRA, custom Webpack, etc.).
 
+The table below lists them in their required pipeline order (the same order they must appear in `babel.config.js`):
+
 | Plugin                        | What it does                                                                                                   |
 | :---------------------------- | :------------------------------------------------------------------------------------------------------------- |
 | `intlayerExtractBabelPlugin`  | Scans `.content.ts` files and writes compiled dictionaries to `.intlayer/`                                     |
-| `intlayerOptimizeBabelPlugin` | Rewrites `useIntlayer('key')` → `useDictionary(hash)` and injects the matching dictionary `import`             |
 | `intlayerPurgeBabelPlugin`    | Scans all source files, removes **unused content fields** from compiled `.intlayer/**/*.json` dictionary files |
 | `intlayerMinifyBabelPlugin`   | **Renames content field keys** to short alphabetic aliases (`title` → `a`) in both JSON files and source code  |
+| `intlayerOptimizeBabelPlugin` | Rewrites `useIntlayer('key')` → `useDictionary(hash)` and injects the matching dictionary `import`             |
 
 > **Plugin order matters.** In your `babel.config.js` the purge and minify plugins must appear **before** the optimize plugin. The optimize pass replaces `useIntlayer('key')` with an opaque `useDictionary(hash)` call, erasing the dictionary-key information that the purge and minify passes need to identify which fields are used.
 
@@ -205,9 +210,9 @@ Each Babel plugin has a matching options helper that reads your `intlayer.config
 | Options helper               | Used with                     |
 | :--------------------------- | :---------------------------- |
 | `getExtractPluginOptions()`  | `intlayerExtractBabelPlugin`  |
-| `getOptimizePluginOptions()` | `intlayerOptimizeBabelPlugin` |
 | `getPurgePluginOptions()`    | `intlayerPurgeBabelPlugin`    |
 | `getMinifyPluginOptions()`   | `intlayerMinifyBabelPlugin`   |
+| `getOptimizePluginOptions()` | `intlayerOptimizeBabelPlugin` |
 
 ### Vite plugins (`vite-intlayer`)
 

package/docs/en/compiler.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-09-09
-updatedAt: 2026-03-12
+updatedAt: 2026-06-23
 title: Intlayer Compiler | Automated Content Extraction for i18n
 description: Automate your internationalization process with the Intlayer Compiler. Extract content directly from your components for faster, more efficient i18n in Vite, Next.js, and more.
 keywords:
@@ -20,6 +20,9 @@ slugs:
   - doc
   - compiler
 history:
+  - version: 9.0.0
+    date: 2026-06-24
+    changes: "Add change regarding Intlayer v9"
   - version: 8.2.0
     date: 2026-03-09
     changes: "Update compiler options, add FilePathPattern support"
@@ -64,12 +67,14 @@ As an alternative, to automate your i18n process while keeping full control of y
 
 ## Usage
 
+> The quickest way to wire the compiler in is the interactive setup: run `npx intlayer init --interactive` and select **Compiler**. On Vite there is nothing to configure — the compiler is plugged in directly through the main `intlayer()` plugin (it activates automatically once `compiler.enabled` is set and a `compiler.output` path is configured). On Next.js the command scaffolds the `babel.config.js` shown below. The non-interactive `intlayer init` leaves the compiler setup untouched.
+
 <Tabs>
  <Tab value='vite'>
 
 ### Vite
 
-For Vite-based applications (React, Vue, Svelte, etc.), the easiest way to use the compiler is through the `vite-intlayer` plugin.
+For Vite-based applications (React, Vue, Svelte, etc.), the compiler is bundled directly into the main `intlayer()` plugin from the `vite-intlayer` package. There is no separate plugin to register.
 
 #### Installation
 
@@ -79,20 +84,21 @@ npm install vite-intlayer
 
 #### Configuration
 
-Update your `vite.config.ts` to include the `intlayerCompiler` plugin:
+The `intlayer()` plugin already includes the compiler. It activates automatically once `compiler.enabled` is set and a `compiler.output` path is configured in your `intlayer.config.ts` (see [Custom config](#custom-config) below):
 
 ```ts fileName="vite.config.ts"
 import { defineConfig } from "vite";
-import { intlayer, intlayerCompiler } from "vite-intlayer";
+import { intlayer } from "vite-intlayer";
 
 export default defineConfig({
   plugins: [
-    intlayer(),
-    intlayerCompiler(), // Adds the compiler plugin
+    intlayer(), // The compiler and locale-routing proxy are bundled in
   ],
 });
 ```
 
+> The standalone `intlayerCompiler()` plugin is still exported for advanced setups. Registering it alongside `intlayer()` is safe — the compiler deduplicates itself and runs only once.
+
 See complete tutorial: [Intlayer Compiler with Vite+React](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_vite+react_compiler.md)
 
 #### Framework Support

package/docs/en/configuration.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-13
-updatedAt: 2026-06-17
+updatedAt: 2026-06-23
 title: Configuration
 description: Learn how to configure Intlayer for your application. Understand the various settings and options available to customize Intlayer to your needs.
 keywords:
@@ -14,6 +14,9 @@ slugs:
   - concept
   - configuration
 history:
+  - version: 9.0.0
+    date: 2026-06-24
+    changes: "Add `enableProxy` option to the routing configuration"
   - version: 8.10.0
     date: 2026-06-17
     changes: "Add `format` option to the dictionary configuration"
@@ -229,6 +232,16 @@ const config: IntlayerConfig = {
      */
     mode: "prefix-no-default",
 
+    /**
+     * Enables the Intlayer locale-routing proxy (middleware).
+     * When enabled, the build-tool integration (e.g. the `intlayer()` Vite plugin)
+     * automatically wires the locale detection / redirect / rewrite middleware in
+     * development, preview and production SSR. On Next.js, the `intlayerProxy`
+     * middleware becomes a pass-through when disabled.
+     * Default: true
+     */
+    enableProxy: true,
+
     /**
      * Where to store the user's selected locale.
      * Options: 'cookie', 'localStorage', 'sessionStorage', 'header', or an array of these.
@@ -671,13 +684,14 @@ Defines settings related to the integrated editor, including server port and act
 
 Settings that control routing behavior, including URL structure, locale storage, and middleware handling.
 
-| Field      | Description                                                                                                                                                                  | Type                                                                                                                                                                                                         | Default                | Example                                                                                                                                                                                     | Note                                                                                                                                                                                                                                                                   |
-| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `mode`     | URL routing mode for locale handling.                                                                                                                                        | `'prefix-no-default'` &#124; <br/> `'prefix-all'` &#124; <br/> `'no-prefix'` &#124; <br/> `'search-params'`                                                                                                  | `'prefix-no-default'`  | `'prefix-no-default'`: `/dashboard` (en) or `/fr/dashboard` (fr). `'prefix-all'`: `/en/dashboard`. `'no-prefix'`: locale handled via other means. `'search-params'`: `/dashboard?locale=fr` | Does not impact cookie or locale storage management.                                                                                                                                                                                                                   |
-| `storage`  | Configuration for storing the locale in the client.                                                                                                                          | `false` &#124; <br/> `'cookie'` &#124; <br/> `'localStorage'` &#124; <br/> `'sessionStorage'` &#124; <br/> `'header'` &#124; <br/> `CookiesAttributes` &#124; <br/> `StorageAttributes` &#124; <br/> `Array` | `['cookie', 'header']` | `'localStorage'` <br/> `[{ type: 'cookie', name: 'custom-locale', secure: true }]`                                                                                                          | See Storage Options table below.                                                                                                                                                                                                                                       |
-| `basePath` | The base path for the application URLs.                                                                                                                                      | `string`                                                                                                                                                                                                     | `''`                   | `'/my-app'`                                                                                                                                                                                 | If app is at `https://example.com/my-app, basePath is `'/my-app'`and URLs become`https://example.com/my-app/en`.                                                                                                                                                       |
-| `rewrite`  | Custom URL rewriting rules that override the default routing mode for specific paths. Supports `[param]` dynamic parameters.                                                 | `Record<string, StrictModeLocaleMap<string>>`                                                                                                                                                                | `undefined`            | See example below                                                                                                                                                                           | • Rewrite rules take precedence over `mode`.<br/>• Works with Next.js and Vite.<br/>• `getLocalizedUrl()` automatically applies matching rules.<br/>• See [Custom URL Rewrites](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/custom_url_rewrites.md). |
-| `domains`  | Maps locales to domain hostnames for domain-based routing. When set, URLs for a locale use that domain as the base (absolute URL) and no locale prefix is added to the path. | `Partial<Record<Locale, string>>`                                                                                                                                                                            | `undefined`            | `{ zh: 'intlayer.zh', fr: 'intlayer.org' }`                                                                                                                                                 | • Protocol defaults to `https://` when not included in the hostname.<br/>• The domain itself identifies the locale, so no `/zh/` prefix is added.<br/>• `getLocalizedUrl('/', 'zh')` returns `https://intlayer.zh/`.                                                   |
+| Field         | Description                                                                                                                                                                  | Type                                                                                                                                                                                                         | Default                | Example                                                                                                                                                                                     | Note                                                                                                                                                                                                                                                                                                                                 |
+| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `mode`        | URL routing mode for locale handling.                                                                                                                                        | `'prefix-no-default'` &#124; <br/> `'prefix-all'` &#124; <br/> `'no-prefix'` &#124; <br/> `'search-params'`                                                                                                  | `'prefix-no-default'`  | `'prefix-no-default'`: `/dashboard` (en) or `/fr/dashboard` (fr). `'prefix-all'`: `/en/dashboard`. `'no-prefix'`: locale handled via other means. `'search-params'`: `/dashboard?locale=fr` | Does not impact cookie or locale storage management.                                                                                                                                                                                                                                                                                 |
+| `enableProxy` | Enables the Intlayer locale-routing proxy (middleware).                                                                                                                      | `boolean`                                                                                                                                                                                                    | `true`                 | `false`                                                                                                                                                                                     | When enabled, the build-tool integration (e.g. the `intlayer()` Vite plugin) automatically wires the locale detection / redirect / rewrite middleware in development, preview and production SSR. On Next.js, the `intlayerProxy` middleware becomes a pass-through when disabled. Set to `false` to handle locale routing yourself. |
+| `storage`     | Configuration for storing the locale in the client.                                                                                                                          | `false` &#124; <br/> `'cookie'` &#124; <br/> `'localStorage'` &#124; <br/> `'sessionStorage'` &#124; <br/> `'header'` &#124; <br/> `CookiesAttributes` &#124; <br/> `StorageAttributes` &#124; <br/> `Array` | `['cookie', 'header']` | `'localStorage'` <br/> `[{ type: 'cookie', name: 'custom-locale', secure: true }]`                                                                                                          | See Storage Options table below.                                                                                                                                                                                                                                                                                                     |
+| `basePath`    | The base path for the application URLs.                                                                                                                                      | `string`                                                                                                                                                                                                     | `''`                   | `'/my-app'`                                                                                                                                                                                 | If app is at `https://example.com/my-app, basePath is `'/my-app'`and URLs become`https://example.com/my-app/en`.                                                                                                                                                                                                                     |
+| `rewrite`     | Custom URL rewriting rules that override the default routing mode for specific paths. Supports `[param]` dynamic parameters.                                                 | `Record<string, StrictModeLocaleMap<string>>`                                                                                                                                                                | `undefined`            | See example below                                                                                                                                                                           | • Rewrite rules take precedence over `mode`.<br/>• Works with Next.js and Vite.<br/>• `getLocalizedUrl()` automatically applies matching rules.<br/>• See [Custom URL Rewrites](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/custom_url_rewrites.md).                                                               |
+| `domains`     | Maps locales to domain hostnames for domain-based routing. When set, URLs for a locale use that domain as the base (absolute URL) and no locale prefix is added to the path. | `Partial<Record<Locale, string>>`                                                                                                                                                                            | `undefined`            | `{ zh: 'intlayer.zh', fr: 'intlayer.org' }`                                                                                                                                                 | • Protocol defaults to `https://` when not included in the hostname.<br/>• The domain itself identifies the locale, so no `/zh/` prefix is added.<br/>• `getLocalizedUrl('/', 'zh')` returns `https://intlayer.zh/`.                                                                                                                 |
 
 **`rewrite` example**:
 

package/docs/en/custom_domains.md

@@ -165,6 +165,8 @@ GET intlayer.zh/about
 
 The `intlayerProxy` Vite plugin applies the same logic during development:
 
+> Since Intlayer v9, `intlayerProxy()` is bundled directly into the `intlayer()` plugin and enabled by default through the `routing.enableProxy` option (`true` by default). Registering it separately as shown below is now optional — it is kept for backward compatibility and for setups that need to control plugin order. Set `routing.enableProxy: false` to opt out. See the [v9 release notes](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/releases/v9.md).
+
 ```typescript fileName="vite.config.ts"
 import { defineConfig } from "vite";
 import { intlayerProxy } from "vite-intlayer";

package/docs/en/custom_url_rewrites.md

@@ -340,6 +340,8 @@ export function middleware(request: NextRequest) {
 
 For SolidJS, Vue, and Svelte, the `intlayerProxy` Vite plugin manages the rewrites during development.
 
+> Since Intlayer v9, `intlayerProxy()` is bundled directly into the `intlayer()` plugin and enabled by default through the `routing.enableProxy` option (`true` by default). Registering it separately as shown below is now optional — it is kept for backward compatibility and for setups that need to control plugin order. Set `routing.enableProxy: false` to opt out. See the [v9 release notes](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/releases/v9.md).
+
 ```typescript fileName="vite.config.ts"
 import { defineConfig } from "vite";
 import { intlayerProxy } from "vite-intlayer";

package/docs/en/intlayer_with_adonisjs.md

@@ -59,24 +59,40 @@ See [Application Template](https://github.com/aymericzip/intlayer-adonis-templat
 
 To begin using `adonis-intlayer`, install the package using npm:
 
+```bash packageManager="npm"
+npx intlayer-cli init --interactive
+```
+
+```bash packageManager="pnpm"
+pnpm dlx intlayer-cli init --interactive
+```
+
+```bash packageManager="yarn"
+yarn dlx intlayer-cli init --interactive
+```
+
+```bash packageManager="bun"
+bunx intlayer-cli init --interactive
+```
+
+> the `--interactive` flag is optional. Use `intlayer-cli init` if you're an AI agent.
+
+> This command will detect your environment and install the required packages. For example:
+
 ```bash packageManager="npm"
 npm install intlayer adonis-intlayer
-npx intlayer init
 ```
 
 ```bash packageManager="pnpm"
 pnpm add intlayer adonis-intlayer
-pnpm intlayer init
 ```
 
 ```bash packageManager="yarn"
 yarn add intlayer adonis-intlayer
-yarn intlayer init
 ```
 
 ```bash packageManager="bun"
 bun add intlayer adonis-intlayer
-bun x intlayer init
 ```
 
 ### Setup

package/docs/en/intlayer_with_analog.md

@@ -118,24 +118,40 @@ See [Application Template](https://github.com/aymericzip/intlayer-analog-templat
 
 Install the necessary packages using npm:
 
+```bash packageManager="npm"
+npx intlayer-cli init --interactive
+```
+
+```bash packageManager="pnpm"
+pnpm dlx intlayer-cli init --interactive
+```
+
+```bash packageManager="yarn"
+yarn dlx intlayer-cli init --interactive
+```
+
+```bash packageManager="bun"
+bunx intlayer-cli init --interactive
+```
+
+> the `--interactive` flag is optional. Use `intlayer-cli init` if you're an AI agent.
+
+> This command will detect your environment and install the required packages. For example:
+
 ```bash packageManager="npm"
 npm install intlayer angular-intlayer vite-intlayer
-npx intlayer init
 ```
 
 ```bash packageManager="pnpm"
 pnpm add intlayer angular-intlayer vite-intlayer
-pnpm intlayer init
 ```
 
 ```bash packageManager="yarn"
 yarn add intlayer angular-intlayer vite-intlayer
-yarn intlayer init
 ```
 
 ```bash packageManager="bun"
 bun add intlayer angular-intlayer vite-intlayer
-bun x intlayer init
 ```
 
 - **intlayer**

package/docs/en/intlayer_with_angular_19.md

@@ -124,28 +124,44 @@ See [Application Template](https://github.com/aymericzip/intlayer-angular-19-tem
 
 Install the necessary packages using npm:
 
+```bash packageManager="npm"
+npx intlayer-cli init --interactive
+```
+
+```bash packageManager="pnpm"
+pnpm dlx intlayer-cli init --interactive
+```
+
+```bash packageManager="yarn"
+yarn dlx intlayer-cli init --interactive
+```
+
+```bash packageManager="bun"
+bunx intlayer-cli init --interactive
+```
+
+> the `--interactive` flag is optional. Use `intlayer-cli init` if you're an AI agent.
+
+> This command will detect your environment and install the required packages. For example:
+
 ```bash packageManager="npm"
 npm install intlayer angular-intlayer
 npm install @angular-builders/custom-webpack --save-dev
-npx intlayer init
 ```
 
 ```bash packageManager="pnpm"
 pnpm add intlayer angular-intlayer
 pnpm add @angular-builders/custom-webpack --save-dev
-pnpm intlayer init
 ```
 
 ```bash packageManager="yarn"
 yarn add intlayer angular-intlayer
 yarn add @angular-builders/custom-webpack --save-dev
-yarn intlayer init
 ```
 
 ```bash packageManager="bun"
 bun add intlayer angular-intlayer
 bun add @angular-builders/custom-webpack --dev
-bun x intlayer init
 ```
 
 - **intlayer**

package/docs/en/intlayer_with_angular_21.md

@@ -123,28 +123,44 @@ See [Application Template](https://github.com/aymericzip/intlayer-angular-21-tem
 
 Install the necessary packages using npm:
 
+```bash packageManager="npm"
+npx intlayer-cli init --interactive
+```
+
+```bash packageManager="pnpm"
+pnpm dlx intlayer-cli init --interactive
+```
+
+```bash packageManager="yarn"
+yarn dlx intlayer-cli init --interactive
+```
+
+```bash packageManager="bun"
+bunx intlayer-cli init --interactive
+```
+
+> the `--interactive` flag is optional. Use `intlayer-cli init` if you're an AI agent.
+
+> This command will detect your environment and install the required packages. For example:
+
 ```bash packageManager="npm"
 npm install intlayer angular-intlayer
 npm install @angular-builders/custom-esbuild --save-dev
-npx intlayer init
 ```
 
 ```bash packageManager="pnpm"
 pnpm add intlayer angular-intlayer
 pnpm add @angular-builders/custom-esbuild --save-dev
-pnpm intlayer init
 ```
 
 ```bash packageManager="yarn"
 yarn add intlayer angular-intlayer
 yarn add @angular-builders/custom-esbuild --save-dev
-yarn intlayer init
 ```
 
 ```bash packageManager="bun"
 bun add intlayer angular-intlayer
 bun add @angular-builders/custom-esbuild --dev
-bun x intlayer init
 ```
 
 - **intlayer**