@intlayer/docs 9.5.6 → 9.5.8

package/docs/en/agent_skills.md

@@ -99,7 +99,7 @@ npx skills add aymericzip/intlayer-skills
 
 - Teaches the agent to use Svelte stores and idiomatic syntax for reactive and type-safe localized content across Svelte and SvelteKit apps.
 
-**intlayer-cms**
+**intlayer-remote-content**
 
 - Allows the agent to integrate and manage remote content, enabling it to handle live-syncing and remote translation workflows via the Intlayer CMS.
 
@@ -114,3 +114,31 @@ npx skills add aymericzip/intlayer-skills
 **intlayer-compiler**
 
 - Simplifies the agent's workflow by enabling automatic content extraction, allowing it to write translatable strings directly in your code without manual dictionary files.
+
+**intlayer-lit**
+
+- Teaches the agent to translate Lit web components with the `useIntlayer` and `useLocale` ReactiveControllers.
+
+**intlayer-vanilla**
+
+- Enables the agent to localize plain JavaScript / TypeScript pages with `vanilla-intlayer`, with or without a bundler.
+
+**intlayer-remix**
+
+- Gives the agent the Remix 3 router middleware and the request-scoped `useIntlayer` / `useLocale` hooks.
+
+**intlayer-backend**
+
+- Equips the agent to translate server responses in Express, Fastify, Hono, NestJS, AdonisJS and Elysia through one shared middleware + `t` / `getIntlayer` pattern.
+
+**intlayer-dev-tools**
+
+- Lets the agent set up the Intlayer tooling around your code: ESLint rules for hardcoded strings, the Language Server, the VS Code and Chrome extensions, the MCP server and CI/CD translation checks.
+
+**intlayer-markdown**
+
+- Teaches the agent to declare Markdown content (`md()`, `.content.md` files, external files) and render it with MDX components, a global `MarkdownProvider`, Suspense and server-side parsing.
+
+**intlayer-compat**
+
+- Guides the agent through migrating from i18next, react-i18next, next-intl, next-i18next, react-intl, vue-i18n or Lingui with compat adapters that keep the original API, so translation calls don't need rewriting.

package/docs/en/benchmark/nextjs.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2026-04-20
-updatedAt: 2026-09-11
+updatedAt: 2026-09-23
 title: Best i18n solution for Next.js in 2026 - Benchmark Report
 description: Compare Next.js internationalization (i18n) libraries like next-intl, next-i18next, and Intlayer. Detailed performance report on bundle size, leakage, and reactivity.
 keywords:
@@ -17,6 +17,9 @@ slugs:
 author: aymericzip
 applicationTemplate: https://github.com/intlayer-org/benchmark-i18n
 history:
+  - version: 9.5.7
+    date: 2026-09-23
+    changes: "Update benchmark results"
   - version: 9.5.1
     date: 2026-09-11
     changes: "Update benchmark results"
@@ -112,19 +115,19 @@ Finally, `Intlayer` applies a build-time optimization so `useIntlayer('my-key')`
 For this benchmark, we compared the following libraries:
 
 - `Base App` (No i18n library)
-- `next-intlayer` (v9.5.1)
-- [`@intlayer/next-intl`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/next-intl.md) (v9.5.1)
-- [`@intlayer/next-i18next`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/next-i18next.md) (v9.5.1)
-- `next-i18next` (v16.3.0)
-- `next-intl` (v4.14.2)
-- `@lingui/core` (v6.6.0)
-- `next-translate` (v3.2.0)
-- `next-international` (v1.3.1)
-- `@inlang/paraglide-js` (v2.15.1)
-- `@tolgee/react` (v7.2.0)
-- `@lingo.dev/compiler` (v0.4.12)
-- `wuchale` (v0.26.6)
-- `gt-next` (v11.1.24)
+- [`next-intlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/next-intlayer/exports.md) (v9.5.6)
+- [`@intlayer/next-intl`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/next-intl.md) (v9.5.6)
+- [`@intlayer/next-i18next`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/next-i18next.md) (v9.5.6)
+- [`next-i18next`](https://github.com/i18next/next-i18next) (v16.3.0)
+- [`next-intl`](https://github.com/amannn/next-intl) (v4.14.2)
+- [`@lingui/core`](https://github.com/lingui/js-lingui) (v6.6.0)
+- [`next-translate`](https://github.com/aralroca/next-translate) (v3.2.0)
+- [`next-international`](https://github.com/QuiiBz/next-international) (v1.3.1)
+- [`@inlang/paraglide-js`](https://github.com/opral/paraglide-js) (v2.15.1)
+- [`@tolgee/react`](https://github.com/tolgee/tolgee-js) (v7.2.0)
+- [`@lingo.dev/compiler`](https://github.com/lingodotdev/lingo.dev) (v0.4.12)
+- [`wuchale`](https://github.com/wuchalejs/wuchale) (v0.26.6)
+- [`gt-next`](https://github.com/generaltranslation/gt) (v11.1.24)
 
 I used `Next.js` version `16.3.4` with the App Router.
 
@@ -214,7 +217,7 @@ Finally, in comparison with other solutions, Paraglide does not use a store (e.g
 
 **(Tolgee)** (`@tolgee/react@7.2.0`):
 
-`Tolgee` addresses many of the issues mentioned earlier. I found it harder to adopt than similar tools. It does not provide type safety, which also makes catching missing keys at compile time harder. I had to wrap Tolgee’s functions with my own to add missing-key detection.
+`Tolgee` addresses many of the issues mentioned earlier. I found it harder to adopt than similar tools. It does not provide type safety, which also makes catching missing keys at compile time harder. I had to wrap Tolgee’s functions with my own to add missing-key detection. The package is also relatively heavy (~14.3kb, which is about 2.8× `next-intlayer`).
 
 **(Next Intl)** (`next-intl@4.14.2`):
 
@@ -240,7 +243,7 @@ Message formats also differ: `next-intl` uses ICU MessageFormat, while `i18next`
 
 `next-translate` is my main recommendation if you like a `t()`-style API. It is elegant via `next-translate-plugin`, loading namespaces through `getStaticProps` with a Webpack / Turbopack loader. It is also one of the lightest options here (~3.5kb). For namespacing, defining namespaces per page or route in config is well thought out and easier to maintain than main alternatives like **next-intl** or **next-i18next**. In version `3.1.2`, I noted that static rendering did not work; Next.js fell back to dynamic rendering.
 
-**(Intlayer)** (`next-intlayer@9.5.1`):
+**(Intlayer)** (`next-intlayer@9.5.6`):
 
 I will not personally judge `next-intlayer` for objectivity’s sake, since it is my own solution.
 

package/docs/en/benchmark/solid.md

@@ -1,8 +1,8 @@
 ---
 createdAt: 2026-04-20
-updatedAt: 2026-09-11
+updatedAt: 2026-09-23
 title: Best i18n solution for Solid in 2026 - Benchmark Report
-description: Compare Solid internationalization libraries like solid-primitives, solid-i18next, and Intlayer. Detailed performance report on bundle size, leakage, and reactivity.
+description: Compare Solid internationalization libraries like solid-primitives, solid-i18next, Tolgee, and Intlayer. Detailed performance report on bundle size, leakage, and reactivity.
 keywords:
   - benchmark
   - i18n
@@ -17,6 +17,9 @@ slugs:
 author: aymericzip
 applicationTemplate: https://github.com/intlayer-org/benchmark-i18n-solid-template
 history:
+  - version: 9.5.7
+    date: 2026-09-23
+    changes: "Update benchmark results"
   - version: 9.5.1
     date: 2026-09-11
     changes: "Update benchmark results"
@@ -65,9 +68,10 @@ The other impact is on developer experience: how you declare content, types, nam
 
 ## TL;DR
 
-- **Intlayer**: Recommended choice for professional Solid applications needing advanced features and optimization (v9.5.0).
+- **Intlayer**: Recommended choice for professional Solid applications needing advanced features and optimization (v9.5.6).
 - **@solid-primitives/i18n**: Excellent lightweight alternative for simple projects, though lacks advanced features like lazy loading.
 - **solid-i18next**: Standard but heavy option (~3.5× Intlayer) with same downsides as React i18next.
+- **Tolgee**: Feature-rich translation platform, but fairly heavy (~12.7kb, about 3.0× Intlayer), lacks dedicated Solid primitives (relies on @tolgee/web), and in static setups can leak translations across pages (90% page leak).
 - **Paraglide**: Innovative approach but complex DX and tree-shaking issues in some setups.
 
 ## Test your app
@@ -100,10 +104,11 @@ Syntaxes built around `t('a.b.c')` are very convenient but often encourage keepi
 For this benchmark, we compared the following libraries:
 
 - `Base App` (No i18n library)
-- `solid-intlayer` (v9.5.0)
-- `@solid-primitives/i18n` (v2.2.1)
-- `i18next` (v26.0.8) + `@mbarzda/solid-i18next` (v1.4.1)
-- `@inlang/paraglide-js` (v2.25.1)
+- [`solid-intlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/solid-intlayer/exports.md) (v9.5.6)
+- [`@solid-primitives/i18n`](https://github.com/solidjs-community/solid-primitives/tree/main/packages/i18n) (v2.2.1)
+- [`i18next`](https://github.com/i18next/i18next) (v26.0.8) + [`@mbarzda/solid-i18next`](https://github.com/mbarzda/solid-i18next) (v1.4.1)
+- [`@tolgee/web`](https://github.com/tolgee/tolgee-js) (v7.2.0)
+- [`@inlang/paraglide-js`](https://github.com/opral/paraglide-js) (v2.25.1)
 
 The framework is `Solid` with a multilingual app of **10 pages** and **10 languages**.
 
@@ -147,7 +152,7 @@ I ran the same multilingual app in a real browser for every stack, then wrote do
 
 GitHub stars are a strong indicator of a project's popularity, community trust, and long-term relevance. While not a direct measure of technical quality, they reflect how many developers find the project useful, follow its progress, and are likely to adopt it. For estimating the value of a project, stars help compare traction across alternatives and provide insights into ecosystem growth.
 
-[![Star History Chart](https://api.star-history.com/chart?repos=solidjs-community%2Fsolid-primitives%2Cmbarzda%2Fsolid-i18next%2Copral%2Fparaglide-js%2Caymericzip%2Fintlayer&type=date&legend=top-left)](https://star-history.com/#solidjs-community/solid-primitives&mbarzda/solid-i18next&opral/paraglide-js&aymericzip/intlayer)
+[![Star History Chart](https://api.star-history.com/chart?repos=solidjs-community%2Fsolid-primitives%2Cmbarzda%2Fsolid-i18next%2Copral%2Fparaglide-js%2Ctolgee%2Ftolgee-js%2Caymericzip%2Fintlayer&type=date&legend=top-left)](https://star-history.com/#solidjs-community/solid-primitives&mbarzda/solid-i18next&opral/paraglide-js&tolgee/tolgee-js&aymericzip/intlayer)
 
 ## Results in detail
 
@@ -170,6 +175,18 @@ Still, it shares the same major downsides as stacks built on `t('a.b.c')`: optim
 Solid primitive is extremely light and efficient, I recommend that solution for light projects, but it can quickly become lacking features for professional solutions including cookie management, proxy redirection, formatters etc.
 It also misses lazy loading and scoping namespaces for page size optimization.
 
+**(Tolgee)** (`@tolgee/web@7.2.0`):
+
+`Tolgee` provides a feature-rich internationalization platform with in-context editing capabilities.
+
+On Solid, there is currently no dedicated official adapter (such as `@tolgee/solid`), requiring developers to integrate via `@tolgee/web` with custom signals.
+
+The package is fairly heavy (~12.7kb, which is about 3.0× `solid-intlayer`).
+
+Without a granular per-page splitting mechanism in Solid, all translations load into memory upfront in static setups. This leads to heavy bundle leakage (44.5% locale leakage, 90.0% page leakage) and average page bundle sizes of ~91.8kb (compared to ~35.8kb for Intlayer).
+
+Language switch responsiveness is very fast (0.6ms), matching Solid's fine-grained reactivity, though hydration overhead is higher (~5.6ms vs ~3.0ms for Intlayer).
+
 **(Paraglide)** (`@inlang/paraglide-js@2.25.1`):
 
 `Paraglide` offers an innovative, well-thought-out approach. Even so, in this benchmark the tree-shaking their company advertises did not work for my implementation. The workflow and DX are also more complex than other options.
@@ -178,7 +195,7 @@ Finally, in comparison with other solutions, Paraglide does not use a store (e.g
 
 ### 3 - Recommendations
 
-**(Intlayer)** (`solid-intlayer@9.5.0`):
+**(Intlayer)** (`solid-intlayer@9.5.6`):
 
 I will not personally judge `solid-intlayer` for objectivity’s sake, since it is my own solution.
 

package/docs/en/benchmark/svelte.md

@@ -1,8 +1,8 @@
 ---
 createdAt: 2026-04-20
-updatedAt: 2026-09-11
+updatedAt: 2026-09-23
 title: Best i18n solution for Svelte in 2026 - Benchmark Report
-description: Compare Svelte internationalization libraries like svelte-i18n, Paraglide, and Intlayer. Detailed performance report on bundle size, leakage, and reactivity.
+description: Compare Svelte internationalization libraries like svelte-i18n, Paraglide, Tolgee, and Intlayer. Detailed performance report on bundle size, leakage, and reactivity.
 keywords:
   - benchmark
   - i18n
@@ -17,6 +17,9 @@ slugs:
 author: aymericzip
 applicationTemplate: https://github.com/intlayer-org/benchmark-i18n-svelte-template
 history:
+  - version: 9.5.7
+    date: 2026-09-23
+    changes: "Update benchmark results"
   - version: 9.5.1
     date: 2026-09-11
     changes: "Update benchmark results"
@@ -65,8 +68,9 @@ The other impact is on developer experience: how you declare content, types, nam
 
 ## TL;DR
 
-- **Intlayer**: The most performance-efficient choice (v9.5.0) with the smallest footprint.
+- **Intlayer**: The most performance-efficient choice (v9.5.6) with the smallest footprint.
 - **Paraglide**: Strong contender for tree-shaking but has a more complex developer experience and reactivity overhead.
+- **Tolgee**: Feature-rich translation platform with in-context editing, but fairly heavy (~13.0kb, about 3.6× Intlayer), and in static setups exhibits significant bundle leakage across pages (90% page leak).
 - **svelte-i18n**: Feature-complete and standard for Svelte, but carries a much larger bundle weight (~4.5× Intlayer).
 
 ## Test your app
@@ -99,9 +103,10 @@ Syntaxes built around `t('a.b.c')` are very convenient but often encourage keepi
 For this benchmark, we compared the following libraries:
 
 - `Base App` (No i18n library)
-- `svelte-intlayer` (v9.5.0)
-- `svelte-i18n` (v4.0.1)
-- `@inlang/paraglide-js` (v2.25.1)
+- [`svelte-intlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/svelte-intlayer/exports.md) (v9.5.6)
+- [`svelte-i18n`](https://github.com/kaisermann/svelte-i18n) (v4.0.1)
+- [`@tolgee/svelte`](https://github.com/tolgee/tolgee-js) (v7.2.1)
+- [`@inlang/paraglide-js`](https://github.com/opral/paraglide-js) (v2.25.1)
 
 The framework is `Svelte` with a multilingual app of **10 pages** and **10 languages**.
 
@@ -145,7 +150,7 @@ I ran the same multilingual app in a real browser for every stack, then wrote do
 
 GitHub stars are a strong indicator of a project's popularity, community trust, and long-term relevance. While not a direct measure of technical quality, they reflect how many developers find the project useful, follow its progress, and are likely to adopt it. For estimating the value of a project, stars help compare traction across alternatives and provide insights into ecosystem growth.
 
-[![Star History Chart](https://api.star-history.com/chart?repos=kaisermann%2Fsvelte-i18n%2Copral%2Fparaglide-js%2Caymericzip%2Fintlayer&type=date&legend=top-left)](https://star-history.com/#kaisermann/svelte-i18n&opral/paraglide-js&aymericzip/intlayer)
+[![Star History Chart](https://api.star-history.com/chart?repos=kaisermann%2Fsvelte-i18n%2Copral%2Fparaglide-js%2Ctolgee%2Ftolgee-js%2Caymericzip%2Fintlayer&type=date&legend=top-left)](https://star-history.com/#kaisermann/svelte-i18n&opral/paraglide-js&tolgee/tolgee-js&aymericzip/intlayer)
 
 ## Results in detail
 
@@ -165,6 +170,16 @@ Finally, in comparison with other solutions, Paraglide does not use a store (e.g
 
 > Note on paraglide: the solution inject code in your codebase to import, as a result the metric 'lib size' in the benchmark report is almost 0. Code gen is a good think, because the function used will include only the necessary logic (prefix all vs no prefix, cookie vs storage etc). In comparison Intlayer process to this filtering using env variables injection during the build to force the bundler to tree shake the content depending of the logic. Thanks to this, paraglide and intlayer end up being solution 6-10 times lighter than i18next or next-intl.
 
+**(Tolgee)** (`@tolgee/svelte@7.2.1`):
+
+`Tolgee` provides an all-in-one localization platform with in-context editing and official Svelte integration via `@tolgee/svelte`.
+
+The package is fairly heavy (~13.0kb, which is about 3.6× `svelte-intlayer`).
+
+Without granular per-page splitting in Svelte, all translations load into memory upfront in static setups. This causes substantial bundle leakage (50.0% locale leakage, 90.0% page leakage) and average page bundle sizes of ~100.7kb (compared to ~59.0kb for Intlayer).
+
+Language switch responsiveness is very fast (0.5ms), benefiting from Svelte's reactive stores, though hydration overhead is slightly higher (~6.2ms vs ~5.5ms for Intlayer).
+
 **(svelte-i18n)** (`svelte-i18n@4.0.1`):
 
 This solution answers all needs for i18n in a Svelte project. But as it's the case for i18next or other main i18n solutions it's a bit heavy (~16.6kb, which is about 4.5× `svelte-intlayer`).

package/docs/en/benchmark/tanstack.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2026-04-20
-updatedAt: 2026-09-11
+updatedAt: 2026-09-23
 title: Best i18n solution for TanStack Start in 2026 - Benchmark Report
 description: Compare TanStack Start internationalization libraries like react-i18next, use-intl, and Intlayer. Detailed performance report on bundle size, leakage, and reactivity.
 keywords:
@@ -17,6 +17,9 @@ slugs:
 author: aymericzip
 applicationTemplate: https://github.com/intlayer-org/benchmark-i18n-tanstack-start-template
 history:
+  - version: 9.5.7
+    date: 2026-09-23
+    changes: "Update benchmark results"
   - version: 9.5.1
     date: 2026-09-11
     changes: "Update benchmark results"
@@ -65,7 +68,7 @@ The other impact is on developer experience: how you declare content, types, nam
 
 ## TL;DR
 
-- **Intlayer**: Provides the best performance and smallest bundle size (v9.5.1) for TanStack Start.
+- **Intlayer**: Provides the best performance and smallest bundle size (v9.5.6) for TanStack Start.
 - **react-i18next** & **use-intl**: Mature alternatives with large ecosystems, but significantly heavier and more complex to optimize.
 - **Paraglide**: Innovative tree-shaking idea that does not work in practice. Complex DX and reactivity overhead in TanStack Start.
 - **Avoid**: **General Translation (GT)** and **Lingo.dev** due to severe performance issues, AI quota limits, and vendor lock-in.
@@ -100,18 +103,19 @@ Syntaxes built around `const t = useTranslation()` + `t('a.b.c')` are very conve
 For this benchmark, we compared the following libraries:
 
 - `Base App` (No i18n library)
-- `react-intlayer` (v9.5.1)
-- `@intlayer/use-intl` (v9.5.1)
-- [`@intlayer/lingui`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/lingui.md) (v9.5.1)
-- `react-i18next` (v17.0.13)
-- `use-intl` (v4.14.2)
-- `@lingui/core` (v6.6.0)
-- `@inlang/paraglide-js` (v2.15.1)
-- `@tolgee/react` (v7.2.0)
-- `react-intl` (v10.1.26)
-- `wuchale` (v0.26.6)
-- `gt-react` (v10.18.3)
-- `lingo.dev` (v0.138.7)
+- [`react-intlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/react-intlayer/exports.md) (v9.5.6)
+- [`@intlayer/use-intl`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/next-intl.md) (v9.5.6)
+- [`@intlayer/lingui`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/lingui.md) (v9.5.6)
+- [`@intlayer/react-i18next`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/react-i18next.md) (v9.5.6)
+- [`react-i18next`](https://github.com/i18next/react-i18next) (v17.0.13)
+- [`use-intl`](https://github.com/amannn/next-intl/tree/main/packages/use-intl) (v4.14.2)
+- [`@lingui/core`](https://github.com/lingui/js-lingui) (v6.6.0)
+- [`@inlang/paraglide-js`](https://github.com/opral/paraglide-js) (v2.15.1)
+- [`@tolgee/react`](https://github.com/tolgee/tolgee-js) (v7.2.0)
+- [`react-intl`](https://github.com/formatjs/formatjs) (v10.1.26)
+- [`wuchale`](https://github.com/wuchalejs/wuchale) (v0.26.6)
+- [`gt-react`](https://github.com/generaltranslation/gt) (v10.18.3)
+- [`lingo.dev`](https://github.com/lingodotdev/lingo.dev) (v0.138.7)
 
 The framework is `TanStack Start` with a multilingual app of **10 pages** and **10 languages**.
 
@@ -201,13 +205,13 @@ Finally, in comparison with other solutions, Paraglide does not use a store (e.g
 
 `Tolgee` addresses many of the issues mentioned earlier. I found it harder to get started with than other tools with similar approaches. It does not provide type safety, which also makes catching missing keys at compile time much harder. I had to wrap Tolgee’s APIs with my own to add missing-key detection.
 
-The package is fairly heavy (~11.1kb, which is more than 2× `react-intlayer`).
+The package is fairly heavy (~13.8kb, which is about 2.9× `react-intlayer`).
 
 On TanStack Start I also had reactivity problems: on locale change I had to force the provider to rerender and subscribe to locale-change events so loading in another language behaved correctly.
 
 **(use-intl)** (`use-intl@4.14.2`):
 
-`use-intl` is the most fashionable “intl” piece in the React ecosystem (same family as `next-intl`) and is often pushed by AI agents, but in my view wrongly so in a performance-first setting. Getting started is fairly simple. In practice, the process to optimize and limit leakage is quite complex. Likewise, combining dynamic loading + namespacing + TypeScript types slows development a lot. The package is also fairly heavy (~14.1kb, which is more than 2.5× `react-intlayer`).
+`use-intl` is the most fashionable “intl” piece in the React ecosystem (same family as `next-intl`) and is often pushed by AI agents, but in my view wrongly so in a performance-first setting. Getting started is fairly simple. In practice, the process to optimize and limit leakage is quite complex. Likewise, combining dynamic loading + namespacing + TypeScript types slows development a lot. The package is also fairly heavy (~13.0kb, which is about 2.7× `react-intlayer`).
 
 On TanStack Start you avoid Next.js-specific traps (`setRequestLocale`, static rendering), but the core issue is the same: without strict discipline, the bundle quickly carries too many messages and per-route namespace maintenance becomes painful.
 
@@ -235,7 +239,7 @@ The package is also heavy (~15.3kb, which is about 3× `react-intlayer`).
 
 This TanStack Start benchmark has no direct equivalent to `next-translate` (Next.js plugin + `getStaticProps`). For teams that really want a `t()` API with a mature ecosystem, `react-i18next` and `use-intl` remain “reasonable” choices, but expect to invest a lot of time optimizing to avoid leakage.
 
-**(Intlayer)** (`react-intlayer@9.5.1`):
+**(Intlayer)** (`react-intlayer@9.5.6`):
 
 I will not personally judge `react-intlayer` for objectivity’s sake, since it is my own solution.
 

package/docs/en/benchmark/vue.md

@@ -1,8 +1,8 @@
 ---
 createdAt: 2026-04-20
-updatedAt: 2026-09-11
+updatedAt: 2026-09-23
 title: Best i18n solution for Vue in 2026 - Benchmark Report
-description: Compare Vue internationalization libraries like vue-i18n, fluent-vue, and Intlayer. Detailed performance report on bundle size, leakage, and reactivity.
+description: Compare Vue internationalization libraries like vue-i18n, fluent-vue, Tolgee, and Intlayer. Detailed performance report on bundle size, leakage, and reactivity.
 keywords:
   - benchmark
   - i18n
@@ -17,6 +17,9 @@ slugs:
 author: aymericzip
 applicationTemplate: https://github.com/intlayer-org/benchmark-i18n-vue-template
 history:
+  - version: 9.5.7
+    date: 2026-09-23
+    changes: "Update benchmark results and add Tolgee"
   - version: 9.5.1
     date: 2026-09-11
     changes: "Update benchmark results"
@@ -65,7 +68,8 @@ The other impact is on developer experience: how you declare content, types, nam
 
 ## TL;DR
 
-- **Intlayer**: The most lightweight solution (v9.5.0) with built-in scoping and dynamic loading.
+- **Intlayer**: The most lightweight solution (v9.5.6) with built-in scoping and dynamic loading.
+- **Tolgee**: Effective dynamic loading with zero leakage in dynamic mode, but heavier (~3.7× Intlayer) and lacks built-in compile-time type safety.
 - **vue-i18n**: The industry standard with a rich ecosystem but can be significantly heavier and harder to optimize for code-splitting in large applications.
 - **fluent-vue**: Innovative message organization but lacks type safety and is extremely heavy.
 
@@ -99,10 +103,11 @@ Syntaxes built around `const { t } = useI18n()` + `t('a.b.c')` are very convenie
 For this benchmark, we compared the following libraries:
 
 - `Base App` (No i18n library)
-- `vue-intlayer` (v9.5.0)
-- [`@intlayer/vue-i18n`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/vue-i18n.md) (v9.5.1)
-- `vue-i18n` (v11.4.0)
-- `fluent-vue` (v3.8.2)
+- [`vue-intlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/vue-intlayer/exports.md) (v9.5.6)
+- [`@intlayer/vue-i18n`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compat/vue-i18n.md) (v9.5.6)
+- [`vue-i18n`](https://github.com/intlify/vue-i18n) (v11.4.0)
+- [`fluent-vue`](https://github.com/fluent-vue/fluent-vue) (v3.8.2)
+- [`@tolgee/vue`](https://github.com/tolgee/tolgee-js) (v7.2.0)
 
 The framework is `Vue` with a multilingual app of **10 pages** and **10 languages**.
 
@@ -146,7 +151,7 @@ I ran the same multilingual app in a real browser for every stack, then wrote do
 
 GitHub stars are a strong indicator of a project's popularity, community trust, and long-term relevance. While not a direct measure of technical quality, they reflect how many developers find the project useful, follow its progress, and are likely to adopt it. For estimating the value of a project, stars help compare traction across alternatives and provide insights into ecosystem growth.
 
-[![Star History Chart](https://api.star-history.com/chart?repos=intlify%2Fvue-i18n%2Cfluent-vue%2Ffluent-vue%2Caymericzip%2Fintlayer&type=date&legend=top-left)](https://star-history.com/#intlify/vue-i18n&fluent-vue/fluent-vue&aymericzip/intlayer)
+[![Star History Chart](https://api.star-history.com/chart?repos=intlify%2Fvue-i18n%2Cfluent-vue%2Ffluent-vue%2Ctolgee%2Ftolgee-js%2Caymericzip%2Fintlayer&type=date&legend=top-left)](https://star-history.com/#intlify/vue-i18n&fluent-vue/fluent-vue&tolgee/tolgee-js&aymericzip/intlayer)
 
 ## Results in detail
 
@@ -156,18 +161,22 @@ GitHub stars are a strong indicator of a project's popularity, community trust,
 
 ### 2 - Acceptable solutions
 
+**(Tolgee)** (`@tolgee/vue@7.2.0`):
+
+`Tolgee` addresses many of the issues mentioned earlier, offering dynamic loading that successfully eliminates locale and page leakage (dropping page JS down to ~58.8kb). However, it does not provide built-in compile-time type safety for keys out of the box, making catching missing keys harder. Additionally, the library footprint is relatively heavy (~13.8kb, which is about 3.7× `vue-intlayer`).
+
 **(vue-i18n)** (`vue-i18n@11.4.0`):
 
 - **vue-i18n** is without contestation the most used i18n library for vue, it has a lot of features and a huge ecosystem. but under the hood the solution is quite heavy. even if vue-i18n integrate lazy loading for messages, it miss a scoping feature. In the case of a classic Vue SPA app there is no issue, but for a nuxt app, using @nuxt/i18n, it leads to including the messages from all pages into a single one. For a big nuxt app including more than 10 pages, it can become really problematic.
 
-The package is very heavy (~24.3kb, which is about 6× `vue-intlayer`).
+The package is very heavy (~24.1kb, which is about 6.5× `vue-intlayer`).
 
 **(fluent-vue)** (`fluent-vue@3.8.2`):
 
-- **fluent-vue** offer one inovation attempt thought the .ftl format. the message organization is great, easier to get started. but in practice, the lack of typesafty increase the risk of error and can quickly become time consuming to debug. Moreever, that solution load the messages using a vite plugin that force the loading of all the content in all languages into each page. Additionally this is an extremely heavy solution (~29.7kb, which is about 7.5× `vue-intlayer`).
+- **fluent-vue** offer one inovation attempt thought the .ftl format. the message organization is great, easier to get started. but in practice, the lack of typesafty increase the risk of error and can quickly become time consuming to debug. Moreever, that solution load the messages using a vite plugin that force the loading of all the content in all languages into each page. Additionally this is an extremely heavy solution (~29.7kb, which is about 8× `vue-intlayer`).
 
 ### 3 - Recommendations
 
-**(Intlayer)** (`vue-intlayer@9.5.0`):
+**(Intlayer)** (`vue-intlayer@9.5.6`):
 
 I will not personally judge `vue-intlayer` for objectivity’s sake, since it is my own solution.

package/docs/en/chrome_extension.md

@@ -0,0 +1,130 @@
+---
+createdAt: 2026-09-22
+updatedAt: 2026-09-22
+title: Chrome & Firefox Extension, i18n & SEO Scanner
+description: Inspect the i18n setup of any website with the Intlayer Chrome extension. Detect the framework, i18n library, locales, hreflang and SEO tags, and run a full i18n SEO audit.
+keywords:
+  - Chrome Extension
+  - i18n Scanner
+  - hreflang Checker
+  - Multilingual SEO
+  - Intlayer
+  - Localization
+  - Development Tools
+slugs:
+  - doc
+  - chrome-extension
+history:
+  - version: 9.5.6
+    date: 2026-09-22
+    changes: "Init history"
+author: aymericzip
+---
+
+# Chrome & Firefox Extension: i18n & SEO Scanner
+
+## Overview
+
+[**Intlayer i18n Scanner**](https://chromewebstore.google.com/detail/intlayer_i18n_scanner/pmlehcgmjmfimmjnembihbakhnheiabc) is the official Chrome extension for **Intlayer**. Open it on any website to see how the site handles internationalization: which framework and i18n library it uses, which locales it exposes, and whether its multilingual SEO tags are set up correctly.
+
+It works on every website, whether or not it uses Intlayer.
+
+![Intlayer Chrome Extension](https://github.com/aymericzip/intlayer/blob/main/docs/assets/chrome_extension.png?raw=true)
+
+[Chrome extension link](https://chromewebstore.google.com/detail/intlayer_i18n_scanner/pmlehcgmjmfimmjnembihbakhnheiabc)
+
+[Firefox add-on link](https://addons.mozilla.org/en-US/firefox/addon/intlayer-i18n-scanner/)
+
+## Features
+
+- **Technology detection**: identifies the framework (Next.js, Nuxt, Astro, SvelteKit, Angular, Vue.js, Qwik, React, Gatsby, WordPress) and the i18n library (Intlayer, i18next, Vue I18n, @nuxtjs/i18n, Angular @angular/localize, next-intl / next-i18next, Weglot, Localize, WPML, Polylang). Each detection shows the evidence that triggered it, such as a global variable, a cookie or a DOM marker.
+- **Locales**: lists the locales found in the `lang` attribute, hreflang and `og:locale` tags, the URL locale prefix, and locale cookies or storage entries.
+- **SEO i18n tags**: checks `html lang`, `html dir`, the canonical link, hreflang tags, `x-default`, `og:locale` and the ratio of localized internal links.
+- **Navigate across locales**: switches the current page to any of its localized versions in one click, based on its hreflang tags.
+- **Search in sitemap**: searches every page listed in the site's sitemap and opens it in the current tab.
+- **Full audit**: runs the same audit as the [i18n SEO Scanner](https://intlayer.org/i18n-seo-scanner) and shows a live score.
+
+## Installation
+
+<Tabs group="browser">
+  <Tab label="Chrome" value="chrome">
+
+Install [**Intlayer i18n Scanner**](https://chromewebstore.google.com/detail/intlayer_i18n_scanner/pmlehcgmjmfimmjnembihbakhnheiabc) from the Chrome Web Store, then pin it to your toolbar.
+
+The extension works in Chrome and in any Chromium based browser that supports Chrome Web Store extensions (Edge, Brave, Arc, Opera).
+
+  </Tab>
+  <Tab label="Firefox" value="firefox">
+
+Install [**Intlayer i18n Scanner**](https://addons.mozilla.org/en-US/firefox/addon/intlayer-i18n-scanner/) from Firefox Add-ons, then pin it to your toolbar.
+
+  </Tab>
+</Tabs>
+
+## Usage
+
+### Inspect a page
+
+1. Open the website you want to inspect.
+2. Click the **Intlayer i18n Scanner** icon in the toolbar.
+3. The popup shows the **Detected technologies**, **Locales** and **SEO i18n tags** sections for the current page.
+
+Detection runs locally in your browser, on the current tab only.
+
+### Navigate between locales
+
+![Intlayer Chrome Extension navigation](https://github.com/aymericzip/intlayer/blob/main/docs/assets/chrome_extension_navigation.png?raw=true)
+
+The **Navigate** section lists the **Localized versions** of the current page, read from its hreflang tags. Click a locale to open that version in the current tab.
+
+Under **Sitemap pages**, type to search the URLs of the site's sitemap, then click a result to open it.
+
+### Run a full audit
+
+![Intlayer Chrome Extension audit score](https://github.com/aymericzip/intlayer/blob/main/docs/assets/chrome_extension_audit_score.png?raw=true)
+
+Scroll to the **Full audit** section and click **Run full i18n audit**. Results stream in as each check completes, grouped into:
+
+- **Page**: `html lang` and `dir` attributes, current locale, hreflang tags, `x-default`, canonical link, localized internal links, language selector, flag icons, and unused locale content shipped in the JavaScript bundle.
+- **Robots.txt**: presence, and whether locale paths stay crawlable.
+- **Sitemap**: presence, every locale listed, alternate links and `x-default`.
+- **Domain**: number of locales discovered across the site.
+
+Each check is marked as passed, warning or failed, and the score summarizes the overall i18n SEO health of the page.
+
+## Privacy and permissions
+
+The extension requests minimal permissions:
+
+- **activeTab** and **scripting**: the detector runs only on the tab you are viewing, and only when you open the popup.
+- **back.intlayer.org**: used only when you run a full audit. The URL of the current page is sent to the Intlayer API to be scanned.
+
+No browsing history is collected and nothing runs in the background.
+
+## FAQ
+
+<FAQ>
+
+<Question title="Does the website need to use Intlayer?">
+
+No. The extension inspects any website, whatever framework or i18n library it uses.
+
+</Question>
+<Question title="Why is a technology not detected?">
+
+Detection relies on what the page exposes in the browser: global variables, cookies, meta tags and DOM markers. Some production builds strip these markers, so a library can be in use without leaving a visible trace.
+
+</Question>
+<Question title="How do I fix the issues found by the audit?">
+
+Most checks map to a routing or metadata setting. With Intlayer, hreflang, canonical, `x-default`, localized links, sitemap and robots.txt are generated from your [configuration](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md). See the integration guide for your framework, for example [Next.js](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_nextjs_16.md), [Nuxt](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_nuxt.md) or [TanStack Start](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_with_tanstack.md).
+
+</Question>
+
+</FAQ>
+
+## Related tools
+
+- [VS Code Extension](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/vs_code_extension.md)
+- [MCP Server](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/mcp_server.md)
+- [LSP Server](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/lsp.md)

package/docs/en/cli/index.md

@@ -1,6 +1,6 @@
 ---
 createdAt: 2024-08-11
-updatedAt: 2026-09-12
+updatedAt: 2026-09-23
 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 a few minutes.
 keywords:
@@ -17,6 +17,12 @@ slugs:
   - concept
   - cli
 history:
+  - version: 9.5.8
+    date: 2026-09-23
+    changes: "Add upgrade command"
+  - version: 9.5.6
+    date: 2026-09-21
+    changes: "Add init infra command"
   - version: 9.5.2
     date: 2026-09-12
     changes: "Replace the `ci` command by the `--ci` flag"
@@ -151,6 +157,8 @@ To see how to configure available locales, or other parameters, refer to the [co
 ### Configuration
 
 - **[Initialize Intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/init.md)** - Set up Intlayer in your project with automatic configuration
+- **[Set Up Infrastructure](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/infra.md)** - Install the desktop app or self-host the CMS with Docker (all-in-one or Compose)
+- **[Upgrade Intlayer Packages](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/upgrade.md)** - List the Intlayer packages of every `package.json` and upgrade them to the latest version
 - **[Manage Configuration](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/configuration.md)** - Get and push your Intlayer configuration to the CMS
 
 ### Documentation Management
@@ -177,6 +185,8 @@ To see how to configure available locales, or other parameters, refer to the [co
 ```json fileName="package.json"
 "scripts": {
   "intlayer:init": "npx intlayer init",
+  "intlayer:infra": "npx intlayer init infra",
+  "intlayer:upgrade": "npx intlayer upgrade",
   "intlayer:login": "npx intlayer login",
   "intlayer:build": "npx intlayer build",
   "intlayer:watch": "npx intlayer build --watch",