@intlayer/docs 9.5.0 → 9.5.2

package/docs/en-GB/cli/index.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-11
-updatedAt: 2026-03-31
+updatedAt: 2026-09-12
 title: CLI - All Intlayer CLI commands for your multilingual website
 description: Discover how to use the Intlayer CLI to manage your multilingual website. Follow the steps in this online documentation to set up your project in minutes.
 keywords:
@@ -17,6 +17,9 @@ slugs:
   - concept
   - cli
 history:
+  - version: 9.5.2
+    date: 2026-09-12
+    changes: "Replace the `ci` command by the `--ci` flag"
   - version: 9.0.0
     date: 2026-06-11
     changes: "Added scan command"
@@ -160,10 +163,6 @@ To learn how to configure the available languages or other parameters, take a lo
 - **[Editor Commands](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/cli/editor.md)** - Use the Intlayer Editor commands
 - **[Live Sync Commands](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/cli/live.md)** - Use Live Sync to apply content changes from CMS in real time
 
-### CI/CD and Automation
-
-- **[CI Command](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/cli/ci.md)** - Execute Intlayer commands with automatically injected credentials for CI/CD flows
-
 ### Auditing & Diagnostics
 
 - **[Scan Website](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/cli/scan.md)** - Measure page size and audit i18n/SEO health of any public URL

package/docs/en-GB/cli/live.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-11
-updatedAt: 2025-11-22
+updatedAt: 2026-09-12
 title: Live Sync Commands
 description: Learn how to use Live Sync to reflect CMS content changes at runtime.
 keywords:
@@ -37,6 +37,10 @@ Live Sync allows your app to reflect CMS content changes at runtime. No rebuild
 
   > Example: `npx intlayer dictionary push --env-file .env.production.local`
 
+- **`--ci`**: Run the command in every Intlayer project of the monorepo (or only the current one when run from a project directory). Per-project credentials can be injected via `INTLAYER_PROJECT_CREDENTIALS`, a JSON map of project path to `{ "clientId", "clientSecret" }`.
+
+  > Example: `npx intlayer live --ci`
+
 **Log options:**
 
 - **`--verbose`**: Enable verbose logging for debugging. (defaults to true when using the CLI)

package/docs/en-GB/cli/login.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2025-12-16
-updatedAt: 2025-12-16
+updatedAt: 2026-09-12
 title: CLI - Login
 description: Learn how to use the Intlayer CLI login command to authenticate with the Intlayer CMS and obtain access credentials.
 keywords:
@@ -142,7 +142,7 @@ Intlayer enforces this rather than only documenting it:
 
 Commenting `clientId` out is enough to disable every credentialed behaviour — remote dictionary fetching, CMS access, analytics — even when the environment variables are still defined.
 
-For CI pipelines, prefer the [`ci` command](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/ci.md), which injects the credentials for the duration of a single run instead of persisting them.
+For CI pipelines, prefer the `--ci` flag, which injects the credentials for the duration of a single run instead of persisting them.
 
 ## Manual Configuration
 

package/docs/en-GB/cli/pull.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-11
-updatedAt: 2025-11-22
+updatedAt: 2026-09-12
 title: Pull Dictionaries
 description: Learn how to pull dictionaries from the Intlayer editor and CMS.
 keywords:
@@ -66,6 +66,10 @@ If the [intlayer editor](https://github.com/aymericzip/intlayer/blob/main/docs/d
 
   > Example: `npx intlayer build --no-cache`
 
+- **`--ci`**: Run the command in every Intlayer project of the monorepo (or only the current one when run from a project directory). Per-project credentials can be injected via `INTLAYER_PROJECT_CREDENTIALS`, a JSON map of project path to `{ "clientId", "clientSecret" }`.
+
+  > Example: `npx intlayer pull --ci`
+
 **Environment variables options:**
 
 - **`--env`**: Specify the environment (e.g., `development`, `production`).

package/docs/en-GB/cli/push.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-11
-updatedAt: 2025-11-22
+updatedAt: 2026-09-12
 title: Push Dictionaries
 description: Learn how to push your dictionaries to the Intlayer editor and CMS.
 keywords:
@@ -66,6 +66,10 @@ If the [intlayer editor](https://github.com/aymericzip/intlayer/blob/main/docs/d
 
   > Example: `npx intlayer build --no-cache`
 
+- **`--ci`**: Run the command in every Intlayer project of the monorepo (or only the current one when run from a project directory). Per-project credentials can be injected via `INTLAYER_PROJECT_CREDENTIALS`, a JSON map of project path to `{ "clientId", "clientSecret" }`.
+
+  > Example: `npx intlayer push --ci`
+
 **Environment variables options:**
 
 - **`--env`**: Specify the environment (e.g., `development`, `production`). Useful if you use environment variables in your Intlayer configuration file.

package/docs/en-GB/cli/scan.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2026-06-11
-updatedAt: 2026-06-11
+updatedAt: 2026-09-12
 title: Scan Website
 description: Learn how to use the Intlayer CLI scan command to measure page size and audit the i18n/SEO health of any website.
 keywords:
@@ -18,6 +18,9 @@ slugs:
   - cli
   - scan
 history:
+  - version: 9.5.2
+    date: 2026-09-12
+    changes: "Add `--ci` flag"
   - version: 9.0.0
     date: 2026-06-11
     changes: "Added scan command"
@@ -112,6 +115,7 @@ Output the full scan result as a JSON object instead of a formatted report. Usef
 - **`-e, --env`** — Target environment (e.g. `development`, `production`).
 - **`--env-file`** — Path to a custom `.env` file.
 - **`--no-cache`** — Disable configuration cache.
+- **`--ci`** — Run the command in every Intlayer project of the monorepo (or only the current one when run from a project directory). Per-project credentials can be injected via `INTLAYER_PROJECT_CREDENTIALS`, a JSON map of project path to `{ "clientId", "clientSecret" }`.
 - **`--verbose`** — Enable verbose logging (default in CLI mode).
 - **`--prefix`** — Custom log prefix.
 

package/docs/en-GB/cli/standalone.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-11
-updatedAt: 2026-03-31
+updatedAt: 2026-09-12
 title: Standalone Bundle
 description: Learn how to create a standalone JavaScript bundle for app content.
 keywords:
@@ -16,6 +16,9 @@ slugs:
   - cli
   - standalone
 history:
+  - version: 9.5.2
+    date: 2026-09-12
+    changes: "Add `--ci` flag"
   - version: 8.6.4
     date: 2026-03-31
     changes: "Init standalone command documentation"
@@ -61,6 +64,7 @@ bun x intlayer standalone --packages [packages...] [options]
 - `-e, --env [env]` - Environment.
 - `--base-dir [baseDir]` - Base directory.
 - `--no-cache` - Disable cache.
+- `--ci` - Run the command in every Intlayer project of the monorepo (or only the current one when run from a project directory). Per-project credentials can be injected via `INTLAYER_PROJECT_CREDENTIALS`, a JSON map of project path to `{ "clientId", "clientSecret" }`.
 - `--verbose` - Verbose output.
 
 ## Examples:

package/docs/en-GB/cli/test.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-11
-updatedAt: 2025-11-22
+updatedAt: 2026-09-12
 title: Test Missing Translations
 description: Learn how to test and identify missing translations in your dictionaries.
 keywords:
@@ -70,6 +70,10 @@ Total missing required locales: 0
 
   > Example: `npx intlayer build --no-cache`
 
+- **`--ci`**: Run the command in every Intlayer project of the monorepo (or only the current one when run from a project directory). Per-project credentials can be injected via `INTLAYER_PROJECT_CREDENTIALS`, a JSON map of project path to `{ "clientId", "clientSecret" }`.
+
+  > Example: `npx intlayer test --ci`
+
 **Preparation options:**
 
 - **`--build`**: Build the dictionaries before pushing to ensure the content is up to date. True will force the build, false will skip the build, undefined will allow using the cache of the build.

package/docs/en-GB/cli/watch.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-11
-updatedAt: 2025-11-22
+updatedAt: 2026-09-12
 title: Watch Dictionaries
 description: Learn how to watch for changes in your content declaration files and automatically build dictionaries.
 keywords:
@@ -48,3 +48,7 @@ This command is the equivalent of `npx intlayer build --watch --skip-prepare`.
 - **`--with`**: Start command in parallel with the watch.
 
 > Example: `npx intlayer watch --with "next dev --turbopack"`
+
+- **`--ci`**: Run the command in every Intlayer project of the monorepo (or only the current one when run from a project directory). Per-project credentials can be injected via `INTLAYER_PROJECT_CREDENTIALS`, a JSON map of project path to `{ "clientId", "clientSecret" }`.
+
+> Example: `npx intlayer watch --ci`

package/docs/en-GB/compat/i18n-js.md

@@ -28,7 +28,7 @@ Transitioning from the `i18n-js` library to Intlayer is a highly optimised migra
 Execute the following setup command in your repository:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 With `intlayer.config.ts` prepared, you can add Intlayer's alias to your bundler configuration so that any imports of `i18n-js` target the compat package `@intlayer/i18n-js`.

package/docs/en-GB/compat/i18next.md

@@ -33,7 +33,7 @@ Intlayer perfectly replicates the core runtime characteristics of `i18next`. By
 To begin, initialise Intlayer in your project:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 If you are using Vite, include the Intlayer plugin to route imports to `@intlayer/i18next`:

package/docs/en-GB/compat/lingui.md

@@ -28,7 +28,7 @@ If your project currently relies on Lingui's macro-based compilation, transition
 To begin, initialise Intlayer in your project:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 This creates your `intlayer.config.ts`. Ensure you retain `@lingui/babel-plugin-lingui-macro` / `@lingui/swc-plugin` in your build step to run _before_ the Intlayer compiler. Then, use the bundler plugin alias to route `@lingui/core` and `@lingui/react` to `@intlayer/lingui`.

package/docs/en-GB/compat/next-i18next.md

@@ -31,7 +31,7 @@ Intlayer handles all Next.js Pages Router and App Router implementations transpa
 To begin, run:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 This creates the required Intlayer setup file. To swap to Intlayer behind the scenes, update your `next.config.ts`:

package/docs/en-GB/compat/next-intl.md

@@ -31,7 +31,7 @@ Migrating from `next-intl` to Intlayer allows you to maintain your application r
 Execute the following command in your repository:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 This will create an `intlayer.config.ts`. In your `next.config.ts`, use the plugin wrapper to seamlessly inject the `next-intl` aliases towards `@intlayer/next-intl`.

package/docs/en-GB/compat/next-translate.md

@@ -29,7 +29,7 @@ Migrating from `next-translate` to Intlayer is a near drop-in replacement that r
 Initialise Intlayer in your project:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 The CLI will scaffold your configuration. You can then apply the Intlayer plugin in your `next.config.ts`, which injects build-time subpath aliases mapping `next-translate/useTranslation` to `@intlayer/next-translate`.

package/docs/en-GB/compat/ngx-translate.md

@@ -29,7 +29,7 @@ Migrating your Angular application from `ngx-translate` to Intlayer is easy with
 Begin by running:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 This sets up the `intlayer.config.ts`. Replace your `TranslateModule.forRoot()` setups and import aliases appropriately to point to `@intlayer/ngx-translate`.

package/docs/en-GB/compat/nuxtjs-i18n.md

@@ -30,7 +30,7 @@ Migrating your Nuxt application from `@nuxtjs/i18n` to Intlayer is a seamless pr
 To initialise the project, run:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 This will set up `intlayer.config.ts`. Then, add the Intlayer Nuxt module (e.g. `@intlayer/nuxt-i18n`) in your `nuxt.config.ts` modules array. This automatically applies the compat configuration for your application.

package/docs/en-GB/compat/polyglot.md

@@ -29,7 +29,7 @@ If you are using Airbnb's Polyglot.js, migrating to Intlayer is extremely straig
 Simply run the initialisation command in your project:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 This generates `intlayer.config.ts`. You can then utilise the bundler plugin alias to transparently redirect Polyglot imports to `@intlayer/polyglot`.

package/docs/en-GB/compat/react-i18next.md

@@ -31,7 +31,7 @@ Using Intlayer's compat adapter allows you to migrate from `react-i18next` witho
 To initialise the project, run:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 During initialisation, Intlayer will install `@intlayer/react-i18next` and create `intlayer.config.ts`. In your bundler (like Vite), apply the Intlayer plugin:

package/docs/en-GB/compat/react-intl.md

@@ -29,7 +29,7 @@ If your React application uses `react-intl` (FormatJS), transitioning to Intlaye
 Start by running the initialisation command in your project:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 Then, set up the Intlayer Vite or Next.js plugin in your configuration. This plugin injects build-time aliases to redirect `react-intl` imports to `@intlayer/react-intl`.

package/docs/en-GB/compat/svelte-i18n.md

@@ -29,7 +29,7 @@ Moving your Svelte application from `svelte-i18n` to Intlayer takes just a momen
 Simply run the initialisation command in your project:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 This generates `intlayer.config.ts`. Ensure your SvelteKit / Vite plugins are wrapped with Intlayer's alias plugin to seamlessly map `svelte-i18n` to `@intlayer/svelte-i18n`.

package/docs/en-GB/compat/transloco.md

@@ -29,7 +29,7 @@ If your Angular application currently uses `@jsverse/transloco`, you can migrate
 Simply run the initialisation command in your project:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 This will generate the necessary `intlayer.config.ts` configuration. You will then replace your Transloco imports with `@intlayer/transloco` modules or rely on the build aliases.

package/docs/en-GB/compat/vue-i18n.md

@@ -29,7 +29,7 @@ If your Vue application currently uses `vue-i18n`, you can migrate to Intlayer w
 To get started, simply run the initialisation command in your project:
 
 ```bash
-npx intlayer init
+npx intlayer init --interactive
 ```
 
 During the initialisation, Intlayer will set up your configuration file (`intlayer.config.ts`) and prepare your project for migration. You will just need to add the Intlayer plugin to your Vite configuration to automatically alias the `vue-i18n` imports.

package/docs/en-GB/intlayer_with_nextjs_15.md

@@ -975,7 +975,7 @@ bun add @intlayer/swc --dev
 <Tabs>
  <Tab label='Intlayer >=9.5' value='intlayer>=9.5'>
 
-Since Intlayer v9.5, `withIntlayer` starts the content watcher itself, no need extra set up.
+Since next-intlayer v9.5, `withIntlayer` starts the content watcher itself, no need extra set up.
 
  </Tab>
  <Tab label='Intlayer <9.5' value='intlayer<9.5'>

package/docs/en-GB/intlayer_with_nextjs_16.md

@@ -1275,7 +1275,7 @@ bun run build # Or bun run dev
 <Tabs>
  <Tab label='Intlayer >=9.5' value='intlayer>=9.5'>
 
-Since Intlayer v9.5, `withIntlayer` starts the content watcher itself, no need extra set up.
+Since next-intlayer v9.5, `withIntlayer` starts the content watcher itself, no need extra set up.
 
  </Tab>
  <Tab label='Intlayer <9.5' value='intlayer<9.5'>