@intlayer/docs 9.4.4 → 9.5.1

package/docs/en-GB/releases/v9.md

@@ -39,8 +39,6 @@ Welcome to Intlayer v9! This major release marks a huge milestone in simplifying
 
 <TOC levels={[2]} maxDepth={1} />
 
----
-
 ## Compat Adapter Packages
 
 Migrating to Intlayer from popular i18n libraries is now easier than ever. We have created five compat packages that expose the **exact same public APIs** as standard i18n libraries but delegate all translation work to Intlayer at runtime.
@@ -101,8 +99,6 @@ export default defineConfig({
 });
 ```
 
----
-
 ## Mutualized Runtime Resolver
 
 All compat adapters now route translation resolution through a single, highly optimised runtime parser: `@intlayer/core/messageFormat`.
@@ -111,8 +107,6 @@ All compat adapters now route translation resolution through a single, highly op
 - **Message Node Resolver**: Resolves nested nodes: `insert()`, `plural()` (CLDR plural rules), `enu()` (enumeration), `gender()`, HTML tags, arrays, and callable function nodes.
 - **Tokenised Tag Parser**: Supports inline XML/HTML tags and numbered tags (e.g., `<1>children</1>`) to power rich-text rendering out of the box.
 
----
-
 ## Feature Spec: Collections & Variants
 
 Intlayer v9 expands beyond static key-value objects, allowing dictionaries to declare dynamic layout structures that are fully typed end-to-end.
@@ -208,8 +202,6 @@ const product = useIntlayer("product-copy", {
 });
 ```
 
----
-
 ## `@intlayer/analytics`: content exposure tracking & A/B testing
 
 A new optional package, [`@intlayer/analytics`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/analytics.md), tells you which content is actually shown to your visitors — and closes the loop on **Collections & Variants** by letting you A/B test content and measure conversions per variant.
@@ -251,8 +243,6 @@ npm install @intlayer/analytics
 
 Available today for React, Next.js, and React Native (via `react-intlayer`); other framework bindings (Vue, Svelte, Angular, …) are planned, following the same rollout pattern as `@intlayer/editor`. See the [Analytics documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/analytics.md) for the full guide.
 
----
-
 ## Vite Plugin: Bundled Compiler & Proxy
 
 The `intlayer()` Vite plugin now bundles the **compiler** and the **locale-routing proxy** directly, so most projects only need a single plugin in `vite.config.ts`:
@@ -287,8 +277,6 @@ export default config;
 
 The standalone `intlayerCompiler()` and `intlayerProxy()` plugins remain exported for advanced setups. Registering them alongside `intlayer()` is safe — each plugin deduplicates itself and runs only once.
 
----
-
 ## Compiler disabled by default
 
 Starting with Intlayer v9, the **compiler is disabled by default** (`compiler.enabled` now defaults to `false`). To opt in to build-time extraction of your `.content.ts` files, set `compiler.enabled: true` in your configuration:
@@ -308,8 +296,6 @@ export default config;
 
 When the compiler is disabled, Intlayer skips the build-time extraction step and relies on your already-declared dictionaries. Enable it only when you want the bundler plugin (`@intlayer/swc`, `@intlayer/babel`, or the `intlayer()` Vite plugin) to extract content automatically.
 
----
-
 ## React Native: single-package imports
 
 In a React Native or Expo app, you no longer need to juggle both `react-intlayer` and `react-native-intlayer`. The `react-native-intlayer` package now **re-exports the full `react-intlayer` API** (hooks, utilities, and the `/format`, `/html`, and `/markdown` subpaths), and its `IntlayerProvider` automatically applies the React Native polyfills.
@@ -330,8 +316,6 @@ npm install intlayer react-native-intlayer
 
 > Importing from `react-intlayer` keeps working, but `react-native-intlayer` is now the recommended single entry point for React Native — its provider ships the polyfills the web-oriented `react-intlayer` provider does not.
 
----
-
 ## CMS SDK: use Intlayer as a headless content database
 
 Intlayer v9 ships a clean, auto-authenticating SDK in `@intlayer/api` to interact with the CMS programmatically — fetch projects, fetch dictionaries, and push or update them from your own server, scripts, or CI. Authentication (OAuth2 `client_credentials`) is handled and refreshed for you.
@@ -358,8 +342,6 @@ await dictionaryEndpoint(cms).pushDictionaries([myDictionary]);
 
 > Security: the CMS credentials grant write access to your content. Only ever create the authenticator on the **server side** — never ship `clientId` / `clientSecret` to the browser.
 
----
-
 ## Self-Hosting
 
 Intlayer v9 ships first-class support for running your own Intlayer instance with a single command. No Intlayer Cloud account required.
@@ -370,8 +352,6 @@ curl -fsSL https://intlayer.org/install.sh | sh
 
 The installer downloads a `docker-compose.yml` and a `.env`, auto-generates the required secrets, and runs `docker compose up -d`. Everything — the dashboard, the API, the database, object storage, and transactional email — runs locally in containers.
 
----
-
 ## Migration notes from v8
 
 If you are upgrading from v8, note that the v9 does not include breaking changes. But here are the key changes:
@@ -380,8 +360,6 @@ If you are upgrading from v8, note that the v9 does not include breaking changes
 - **Locales & Dialects**: If using external i18n dependencies, add their respective compat adapter plugins in your configuration or bundler setup to automatically rewrite imports.
 - **Custom Selectors**: When calling `useIntlayer`, the second parameter is now reserved for an option object containing `{ locale, item, variant }`. If you previously passed a locale string directly, you can still do so, but using the options object is recommended for advanced selections.
 
----
-
 ## Useful links
 
 - [Compat Adapter Packages Guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/index.md)

package/docs/en-GB/roadmap.md

@@ -27,14 +27,10 @@ author: aymericzip
 
 Intlayer is a content management and internationalisation solution designed to streamline how you declare, manage, and update content across your applications. It offers powerful features such as centralised or distributed content declaration, extensive internationalisation options, Markdown support, conditional rendering, TypeScript/JavaScript/JSON integration, and more. Below is a comprehensive overview of what Intlayer currently provides, followed by upcoming roadmap features.
 
----
-
 ## Table of Contents
 
 <TOC/>
 
----
-
 ## Current Features
 
 ### 1. Content Declaration
@@ -146,8 +142,6 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 >
 > - [Build Configuration](https://intlayer.org/doc/concept/configuration#build-configuration)
 
----
-
 ## Integration with Frameworks & Environments
 
 ### 1. Next.js
@@ -234,8 +228,6 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 >
 > - [Preact](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_with_preact.md)
 
----
-
 ## Visual Editors and CMS
 
 ### 1. Local Visual Editor
@@ -261,21 +253,15 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 >
 > - [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md)
 
----
-
 ## IDE Extensions
 
 - Extensions for major IDEs to provide a **graphical interface** for managing local and remote translations.
 - Features could include auto-generating content declaration files for components, direct integration with the Intlayer CMS, and real-time validation.
 
----
-
 ## MCP Server
 
 - A **MCP server** that allows you to manage your content and translations using an integrated tool in your IDE.
 
----
-
 ## Intlayer CLI
 
 - **Translation and file generation**: Run audits on your content files to generate missing translations and review inconsistencies.
@@ -286,15 +272,11 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 >
 > - [CLI](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/cli/index.md)
 
----
-
 ## Environments
 
 - Use **environment variables** to configure Intlayer differently across production, testing, and local environments.
 - Define which visual editor or remote CMS project to target depending on your environment.
 
----
-
 ## Hot Content Updates
 
 - When using remote dictionaries and the Intlayer CMS, you can **update your application’s content on the fly**, without needing to redeploy.
@@ -303,8 +285,6 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 >
 > - [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md)
 
----
-
 ## Upcoming Features
 
 ### 1. A/B Testing & Personalisation
@@ -333,8 +313,6 @@ Intlayer supports **TypeScript** (also JavaScript) and **JSON** for declaring co
 - Efforts are underway to support **Solid, Svelte, Angular**, and more.
 - Aim to make Intlayer compatible with **any JavaScript-powered application**.
 
----
-
 ## Conclusion
 
 Intlayer aims to be a one-stop solution for content management and internationalisation. It focuses on flexibility (centralised or distributed files), broad language support, easy integration with modern frameworks and bundlers, and powerful AI-driven features. As new capabilities, such as A/B testing, versioning, and automated translations, become available, Intlayer will continue to simplify content workflows and elevate user experiences across different platforms.

package/docs/en-GB/self_hosting.md

@@ -35,8 +35,6 @@ The only external dependency is **MongoDB**: the backend connects to a MongoDB *
 
 <TOC/>
 
----
-
 ## Architecture
 
 ```
@@ -56,8 +54,6 @@ The only external dependency is **MongoDB**: the backend connects to a MongoDB *
 
 Chromium (used for Puppeteer screenshot generation) is bundled inside the backend image. No separate container is needed.
 
----
-
 ## Prerequisites
 
 - **Docker** ≥ 24 and **Docker Compose** ≥ v2. If either is missing, the installer prints the install link and exits.
@@ -66,8 +62,6 @@ Chromium (used for Puppeteer screenshot generation) is bundled inside the backen
 
 Everything else — Bun, Redis, MinIO, Chromium — ships inside the image.
 
----
-
 ## Quick start
 
 ### 1. Run the installer
@@ -136,8 +130,6 @@ curl -fsSL https://intlayer.org/install.sh | INTLAYER_ENV_FILE=./config/intlayer
 
 > The four port variables only change the **host** side of the mapping printed in the `docker run` command. The published image has `http://localhost:3000`, `http://localhost:3100` and `http://localhost:9000` compiled into the dashboard bundle at build time, so remapping them leaves the browser pointing at the old ports. Keep the defaults unless you are building your own image — see [Limitations](#limitations).
 
----
-
 ## Quick start
 
 What the installer does:
@@ -150,8 +142,6 @@ What the installer does:
 
 After the stack is up, open **http://localhost:3000** and create your first account.
 
----
-
 ## Services
 
 | Service     | Image                                | Host port(s)                   | Purpose                                                  |
@@ -165,8 +155,6 @@ After the stack is up, open **http://localhost:3000** and create your first acco
 
 > MinIO port `9000` must be reachable by the browser because uploaded assets (avatars, screenshots) are loaded directly from `S3_PUBLIC_URL=http://localhost:9000/intlayer`.
 
----
-
 ## Environment variables
 
 ### Required
@@ -236,8 +224,6 @@ Set `MAIL_PROVIDER` to activate it. When unset, the default Resend mailer is use
 
 > Precedence: an organisation's own mailer (configured from the **Organisation** dashboard) takes priority over the global mailer, which in turn takes priority over the default Resend key.
 
----
-
 ## Connecting your Intlayer project
 
 Once the stack is running, point your project at the self-hosted backend and dashboard instead of `intlayer.org`.
@@ -299,8 +285,6 @@ const cms = createIntlayerCMS({
 const { data: dictionaries } = await dictionaryEndpoint(cms).getDictionaries();
 ```
 
----
-
 ## Upgrading
 
 This pulls the latest images and restarts containers with `docker compose pull && docker compose up -d`. Existing volumes (`mongo-data`, `redis-data`, `minio-data`) are preserved — no data loss.
@@ -310,8 +294,6 @@ docker compose pull
 docker compose up -d
 ```
 
----
-
 ## Backup and restore
 
 All persistent data lives in three named Docker volumes.
@@ -346,16 +328,12 @@ docker run --rm \
 # Repeat for redis-data and minio-data
 ```
 
----
-
 ## Limitations
 
 - **MongoDB must be external (Atlas).** The backend connects only over `mongodb+srv://` (built from `DB_ID` / `DB_MDP` / `DB_CLUSTER`), so a plain `mongodb://host:27017` — including the container's own bundled `mongod` — cannot be used. Provide a MongoDB Atlas cluster.
 - **No custom domain.** All browser-facing `VITE_*` URLs are inlined into the app at build time, and the published image ships with `localhost` values. The dashboard must be accessed at `http://localhost:3000`; serving it on a public domain would require rebuilding the image with the target URLs baked in and is not supported out of the box.
 - **Email requires a working mailer.** First-run setup enforces email verification, so either `RESEND_API_KEY` or a [global SMTP mailer](#global-mailer) (`MAIL_PROVIDER=smtp` + `MAIL_SMTP_*`) must be configured. After the first admin signs in, each organisation can also configure its own SMTP or Resend mailer from the dashboard.
 
----
-
 ## Troubleshooting
 
 ### Backend crash-loops on first start
@@ -382,8 +360,6 @@ If the `minio-init` one-shot service didn't run (or ran before MinIO was ready),
 docker compose run --rm minio-init
 ```
 
----
-
 ## Useful links
 
 - [Intlayer CMS documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/intlayer_CMS.md)

package/docs/en-GB/testing.md

@@ -24,16 +24,12 @@ author: aymericzip
 
 This guide shows how to automatically verify your dictionaries are complete, catch missing translations before shipping, and test localised UI in your app.
 
----
-
 ## What you can test
 
 - **Missing translations**: fail CI if any required locales are missing for any dictionary.
 - **Localised UI rendering**: render components with a specific locale provider and assert on visible text/attributes.
 - **Build-time audits**: run a quick audit locally via CLI.
 
----
-
 ## Quick start: audit via CLI
 
 Run the audit from your project root:
@@ -64,8 +60,6 @@ Useful flags:
 
 Note: the CLI prints a detailed report but does not exit with a non-zero code on failures. For CI gating, add a unit test (below) that asserts zero missing required locales.
 
----
-
 ## Programmatic test (Vitest/Jest)
 
 Use the Intlayer CLI API to assert there are no missing translations for your required locales.
@@ -112,8 +106,6 @@ How it works:
   - `missingLocales`: union of all missing locales.
   - `missingRequiredLocales`: subset limited to `requiredLocales` (or all locales if `requiredLocales` is not set).
 
----
-
 ## Testing localised UI (React / Next.js)
 
 Render components under an Intlayer provider and assert on visible content.
@@ -160,8 +152,6 @@ Tips:
 - When you need raw string values for attributes (e.g., `aria-label`), access the `.value` field returned by `useIntlayer` in React.
 - Keep dictionaries colocated with components for easier unit testing and cleanup.
 
----
-
 ## Continuous Integration
 
 Add a test that fails the build when required translations are missing.
@@ -211,8 +201,6 @@ pnpm intlayer content test --verbose
 bun x intlayer content test --verbose
 ```
 
----
-
 ## Troubleshooting
 
 - Ensure your Intlayer configuration defines `locales` and (optionally) `requiredLocales`.

package/docs/es/analytics.md

@@ -35,8 +35,6 @@ author: aymericzip
 
 <TOC/>
 
----
-
 ## Qué rastrea
 
 `@intlayer/analytics` agrupa tres tipos de eventos anónimos:

package/docs/es/bundle_optimization.md

@@ -133,8 +133,6 @@ Durante `next build`, `withIntlayer` analiza tus fuentes, reescribe los dicciona
 
 > La purga y la minificación solo se ejecutan en `next build` — el pipeline de optimización está desactivado durante `next dev`.
 
-> También se desactivan cuando hay llamadores de adaptadores de compatibilidad configurados (`swcExtraCallers`, establecidos por los paquetes de compatibilidad como `@intlayer/next-intl` o `@intlayer/react-i18next`): esos puntos de llamada son invisibles para el analizador de uso, por lo que purgar eliminaría campos que el código todavía lee. La reescritura de imports permanece activa.
-
 **Las versiones anteriores (antes de 9.2.1)** requerían `@intlayer/babel` y un `babel.config.js` que declarara `intlayerPurgeBabelPlugin` e `intlayerMinifyBabelPlugin`. Ese archivo ya no es necesario y puede eliminarse.
 
  </Tab>

package/docs/es/cli/index.md

@@ -70,14 +70,10 @@ author: aymericzip
 
 # Intlayer CLI - Todas las comandos de Intlayer CLI para su sitio web multilingüe
 
----
-
 ## Tabla de contenidos
 
 <TOC/>
 
----
-
 ## Instalar paquete
 
 Instale los paquetes necesarios usando npm:

package/docs/es/cli/login.md

@@ -20,8 +20,6 @@ author: aymericzip
 
 # Comando 'login' del CLI de Intlayer
 
----
-
 ## Descripción
 
 El comando `login` del CLI de Intlayer te permite autenticarte con el CMS de Intlayer. Este comando abre automáticamente tu navegador por defecto para completar el proceso de autenticación y recibir las credenciales necesarias (Client ID y Client Secret) para usar los servicios de Intlayer.

package/docs/es/compiler.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-09-09
-updatedAt: 2026-06-23
+updatedAt: 2026-09-08
 title: Intlayer Compiler | Extracción Automática de Contenido para i18n
 description: Automatiza tu proceso de internacionalización con el Intlayer Compiler. Extrae contenido directamente de tus componentes para una i18n más rápida y eficiente en Vite, Next.js y más.
 keywords:
@@ -68,7 +68,7 @@ Como alternativa, para automatizar tu proceso i18n mientras mantienes el control
 
 ## Uso
 
-> 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 `intlayerCompiler()` plugin. On Next.js the command scaffolds the `babel.config.js` shown below. The non-interactive `intlayer init` leaves the compiler setup untouched.
+> La forma más rápida de integrar el compilador es la configuración interactiva: ejecute `npx intlayer init --interactive` y seleccione **Compiler**. En Next.js y Vite, se activa automáticamente una vez que `compiler.enabled` está configurado y se define una ruta `compiler.output`.
 
 <Tabs>
  <Tab value='vite'>
@@ -92,19 +92,13 @@ import { defineConfig } from "vite";
 import { intlayer } from "vite-intlayer";
 
 export default defineConfig({
-  plugins: [
-    intlayer({
-      proxy: {
-        ignore: (req) => req.url?.startsWith("/api"),
-      },
-    }),
-  ],
+  plugins: [intlayer()],
 });
 ```
 
 > El plugin `intlayerCompiler()` independiente sigue siendo exportado para configuraciones avanzadas. Registrarlo junto con `intlayer()` es seguro — el compilador se deduplica a sí mismo y se ejecuta solo una vez.
 
-See complete tutorial: [Intlayer Compiler with Vite+React](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_vite+react_compiler.md)
+See complete tutorial: [Translate Vite and React with Intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_vite+react.md)
 
 #### Soporte de Framework
 
@@ -131,7 +125,33 @@ npm install @intlayer/svelte-compiler
  </Tab>
  <Tab value='nextjs'>
 
-### Next.js (Babel)
+### Next.js
+
+En Next.js, el compilador se ejecuta como un bundler loader, `next-intlayer/extractor-loader`. `withIntlayer` lo registra por ti **tanto** en Turbopack como en webpack, no hay ningún `babel.config.js` que escribir.
+
+#### Instalación
+
+```bash
+npm install @intlayer/babel
+```
+
+#### Configuración
+
+Nada que configurar. Siempre que tu `next.config.ts` pase por `withIntlayer`, instalar `@intlayer/babel` es suficiente para que el loader quede registrado:
+
+```ts fileName="next.config.ts"
+import { withIntlayer } from "next-intlayer/server";
+
+export default withIntlayer({});
+```
+
+El loader se ejecuta en archivos `.tsx` y `.jsx`, antes de `next-swc-loader`, por lo que lee tu JSX original. El contenido declarado en tus componentes se extrae en archivos `.content` y se compila en `.intlayer` a medida que se compila el archivo.
+
+</Tab>
+
+ <Tab value="Babel">
+
+### Babel
 
 Para Next.js u otras aplicaciones basadas en Webpack que usan Babel, puedes configurar el compilador usando el plugin `@intlayer/babel`.
 
@@ -166,8 +186,6 @@ module.exports = {
 
 Esta configuración asegura que el contenido declarado en tus componentes se extraiga automáticamente y se utilice para generar diccionarios durante tu proceso de compilación.
 
-See complete tutorial: [Intlayer Compiler with Next.js](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_nextjs_compiler.md)
-
  </Tab>
 </Tabs>