@intlayer/docs 9.4.4 → 9.5.1

package/docs/en/migration_from_react-i18next_to_intlayer.md

@@ -34,7 +34,6 @@ author: aymericzip
 Instead of loading massive JSON files into your pages, load only the necessary content. Intlayer helps **reduce your bundle and page sizes by up to 50%**.
 
 </Accordion>
-
 <Accordion header="Maintainability">
 
 Scoping your application's content **facilitates maintenance** for large-scale applications. You can duplicate or delete a single feature folder without the mental burden of reviewing your entire content codebase. Additionally, Intlayer is **fully typed** to ensure your content's accuracy.
@@ -42,25 +41,21 @@ Scoping your application's content **facilitates maintenance** for large-scale a
 Intlayer is also the solution with the **most active development** in the i18n ecosystem — issues are fixed fast, new framework adapters land regularly, and the core API is continuously refined based on real-world production feedback.
 
 </Accordion>
-
 <Accordion header="AI Agent">
 
 Co-locating content **reduces the context needed** by Large Language Models (LLMs). Intlayer also comes with a suite of tools, such as a **CLI** to test for missing translations, **[LSP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/lsp.md)**, **[MCP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/mcp_server.md)**, and **[agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/agent_skills.md)**, to make the developer experience (DX) even smoother for AI agents.
 
 </Accordion>
-
 <Accordion header="Automation">
 
 Use automation to translate in your CI/CD pipeline using the LLM of your choice at the cost of your AI provider. Intlayer also offers a **compiler** to automate content extraction, as well as a [web platform](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md) to help **translate in the background**.
 
 </Accordion>
-
 <Accordion header="Performance">
 
 Connecting massive JSON files to components can lead to performance and reactivity issues. Intlayer optimizes your content loading at build time.
 
 </Accordion>
-
 <Accordion header="Scaling with non-dev">
 
 More than just an i18n solution, Intlayer provides a **self-hosted [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md)** and a **[full CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md)** to help you manage your multilingual content in **real-time**, making collaboration with translators, copywriters, and other team members seamless. Content can be stored locally and/or remotely.
@@ -68,8 +63,6 @@ More than just an i18n solution, Intlayer provides a **self-hosted [visual edito
 </Accordion>
 </AccordionGroup>
 
----
-
 ## Migration strategies
 
 There are two complementary strategies for migrating from `react-i18next` / `i18next` to Intlayer:
@@ -80,20 +73,15 @@ There are two complementary strategies for migrating from `react-i18next` / `i18
 
 This guide covers **Strategy 1** first (drop-in compat adapter), then walks through the optional full migration.
 
----
-
 ## Table of Contents
 
 <TOC/>
 
----
-
 ## Quick migration
 
 The following steps are the minimum required to get your existing `react-i18next` app running on Intlayer with zero code changes.
 
 <Steps>
-
 <Step number={1} title="Install Dependencies">
 
 Install the Intlayer core packages and the compat adapters:
@@ -137,7 +125,6 @@ bun add intlayer react-intlayer @intlayer/react-i18next @intlayer/i18next @intla
 > You can keep `react-i18next` and `i18next` installed — the compat adapters use them as `devDependencies` / optional `peerDependencies` for TypeScript types. You don't need to change any `package.json` peers.
 
 </Step>
-
 <Step number={2} title="Configure Intlayer">
 
 The `intlayer init` command creates a starter `intlayer.config.ts`. Update it to match your existing locales and point the `syncJSON` plugin at your message files:
@@ -172,7 +159,6 @@ export default config;
 > **`source`** maps a locale to its JSON file path. **`location`** tells the Intlayer watcher which folder to monitor for changes. The `format: 'i18next'` option ensures that placeholders like `{{name}}` are parsed correctly.
 
 </Step>
-
 <Step number={3} title="Add the Intlayer Plugin to your Bundler">
 
 Wrap your existing bundler config with the compat plugin. It composes the core Intlayer plugin, wires up content watching, and — critically — **injects module aliases** so that your existing `import … from 'react-i18next'` (and `'i18next'`) calls are transparently redirected to `@intlayer/react-i18next` / `@intlayer/i18next` at build time. No source file changes are needed.
@@ -233,14 +219,11 @@ That's it for the quick migration. Your app now runs on Intlayer while keeping e
 > tAbout("counter.label"); // ✓ typed
 > ```
 
----
-
 ## Complete migration
 
 The steps below are optional and can be done incrementally. They unlock the full Intlayer feature set: visual editor, CMS, typed content files, AI-powered translation, and more.
 
 <Steps>
-
 <Step number={4} title="Explicit import renaming (optional)" isOptional={true}>
 
 The Intlayer plugins already handle aliasing at the bundler level. If you prefer to make the dependency explicit in your source files, you can rename imports manually:
@@ -265,7 +248,6 @@ For Next.js (`next-i18next`):
 | `import { useTranslation } from 'next-i18next'`                                | `import { useTranslation } from '@intlayer/next-i18next'`         |
 
 </Step>
-
 <Step number={5} title="Enable AI-Powered Translation Automation" isOptional={true}>
 
 Once Intlayer is wired up, use its CLI to fill missing translations automatically:
@@ -327,8 +309,6 @@ export default config;
 
 </Steps>
 
----
-
 ## What you can delete after migration
 
 Once the compat adapters are in place, the following `react-i18next` / `i18next` boilerplate can be removed:
@@ -341,8 +321,6 @@ Once the compat adapters are in place, the following `react-i18next` / `i18next`
 
 When you are ready to go further, Intlayer **automatically discovers all `.content.ts` and `.content.json` files anywhere in your codebase** (by default, anywhere inside `./src`). You can place a `my-component.content.ts` file right next to your `MyComponent.tsx` and Intlayer will pick it up at build time with no additional configuration — no imports, no registration, no centralized index file needed. This makes co-locating translations with pages and components completely frictionless.
 
----
-
 ## Configure TypeScript
 
 Intlayer uses module augmentation to provide full TypeScript intellisense for your translation keys. Make sure your `tsconfig.json` includes the auto-generated types:
@@ -357,8 +335,6 @@ Intlayer uses module augmentation to provide full TypeScript intellisense for yo
 }
 ```
 
----
-
 ## Git Configuration
 
 Add Intlayer's generated directory to your `.gitignore`:
@@ -368,8 +344,6 @@ Add Intlayer's generated directory to your `.gitignore`:
 .intlayer
 ```
 
----
-
 ## Go Further
 
 - **Visual Editor** — Manage translations visually in your browser: [Intlayer Visual Editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md)

package/docs/en/migration_from_vue-i18n_to_intlayer.md

@@ -33,7 +33,6 @@ author: aymericzip
 Instead of loading massive JSON files into your pages, load only the necessary content. Intlayer helps **reduce your bundle and page sizes by up to 50%**.
 
 </Accordion>
-
 <Accordion header="Maintainability">
 
 Scoping your application's content **facilitates maintenance** for large-scale applications. You can duplicate or delete a single feature folder without the mental burden of reviewing your entire content codebase. Additionally, Intlayer is **fully typed** to ensure your content's accuracy.
@@ -41,25 +40,21 @@ Scoping your application's content **facilitates maintenance** for large-scale a
 Intlayer is also the solution with the **most active development** in the i18n ecosystem — issues are fixed fast, new framework adapters land regularly, and the core API is continuously refined based on real-world production feedback.
 
 </Accordion>
-
 <Accordion header="AI Agent">
 
 Co-locating content **reduces the context needed** by Large Language Models (LLMs). Intlayer also comes with a suite of tools, such as a **CLI** to test for missing translations, **[LSP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/lsp.md)**, **[MCP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/mcp_server.md)**, and **[agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/agent_skills.md)**, to make the developer experience (DX) even smoother for AI agents.
 
 </Accordion>
-
 <Accordion header="Automation">
 
 Use automation to translate in your CI/CD pipeline using the LLM of your choice at the cost of your AI provider. Intlayer also offers a **compiler** to automate content extraction, as well as a [web platform](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md) to help **translate in the background**.
 
 </Accordion>
-
 <Accordion header="Performance">
 
 Connecting massive JSON files to components can lead to performance and reactivity issues. Intlayer optimizes your content loading at build time.
 
 </Accordion>
-
 <Accordion header="Scaling with non-dev">
 
 More than just an i18n solution, Intlayer provides a **self-hosted [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md)** and a **[full CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md)** to help you manage your multilingual content in **real-time**, making collaboration with translators, copywriters, and other team members seamless. Content can be stored locally and/or remotely.
@@ -67,8 +62,6 @@ More than just an i18n solution, Intlayer provides a **self-hosted [visual edito
 </Accordion>
 </AccordionGroup>
 
----
-
 ## Migration strategies
 
 There are two complementary strategies for migrating from `vue-i18n` to Intlayer:
@@ -79,20 +72,15 @@ There are two complementary strategies for migrating from `vue-i18n` to Intlayer
 
 This guide covers **Strategy 1** first (drop-in compat adapter), then walks through the optional full migration.
 
----
-
 ## Table of Contents
 
 <TOC/>
 
----
-
 ## Quick migration
 
 The following steps are the minimum required to get your existing `vue-i18n` app running on Intlayer with zero code changes in your components.
 
 <Steps>
-
 <Step number={1} title="Install Dependencies">
 
 Install the Intlayer core packages and the compat adapter:
@@ -136,7 +124,6 @@ bun add intlayer vue-intlayer @intlayer/vue-i18n @intlayer/sync-json-plugin
 > You can keep `vue-i18n` installed — the compat adapter uses it as a `devDependency` / `peerDependency` for TypeScript types.
 
 </Step>
-
 <Step number={2} title="Configure Intlayer">
 
 The `intlayer init` command creates a starter `intlayer.config.ts`. Update it to match your existing locales and point the `syncJSON` plugin at your message files:
@@ -171,7 +158,6 @@ export default config;
 > **`source`** maps a locale to its JSON file path. **`location`** tells the Intlayer watcher which folder to monitor for changes. The `format: 'icu'` option ensures that placeholders are parsed correctly for `vue-i18n`.
 
 </Step>
-
 <Step number={3} title="Add the Intlayer Plugin to your Bundler">
 
 Wrap your existing bundler config with the compat plugin. It composes the core Intlayer plugin, wires up content watching, and — critically — **injects a module alias** so that your existing `import … from 'vue-i18n'` calls are transparently redirected to `@intlayer/vue-i18n` at build time. No source file changes are needed.
@@ -222,14 +208,11 @@ That's it for the quick migration. Your app now runs on Intlayer while keeping e
 > t("does.not.exist"); // ✗ TypeScript error
 > ```
 
----
-
 ## Complete migration
 
 The steps below are optional and can be done incrementally. They unlock the full Intlayer feature set: visual editor, CMS, typed content files, AI-powered translation, and more.
 
 <Steps>
-
 <Step number={4} title="Explicit import renaming (optional)" isOptional={true}>
 
 The Intlayer plugins already handle aliasing at the bundler level. If you prefer to make the dependency explicit in your source files, you can rename imports manually:
@@ -242,7 +225,6 @@ The Intlayer plugins already handle aliasing at the bundler level. If you prefer
 These are **drop-in replacements** — no changes to call signatures, arguments, or return types are required.
 
 </Step>
-
 <Step number={5} title="Enable AI-Powered Translation Automation" isOptional={true}>
 
 Once Intlayer is wired up, use its CLI to fill missing translations automatically:
@@ -304,8 +286,6 @@ export default config;
 
 </Steps>
 
----
-
 ## What you can delete after migration
 
 Once the compat adapters are in place, the following `vue-i18n` boilerplate can be removed:
@@ -318,8 +298,6 @@ Once the compat adapters are in place, the following `vue-i18n` boilerplate can
 
 When you are ready to go further, Intlayer **automatically discovers all `.content.ts` and `.content.json` files anywhere in your codebase** (by default, anywhere inside `./src`). You can place a `my-component.content.ts` file right next to your `MyComponent.vue` and Intlayer will pick it up at build time with no additional configuration — no imports, no registration, no centralized index file needed. This makes co-locating translations with pages and components completely frictionless.
 
----
-
 ## Configure TypeScript
 
 Intlayer uses module augmentation to provide full TypeScript intellisense for your translation keys. Make sure your `tsconfig.json` includes the auto-generated types:
@@ -334,8 +312,6 @@ Intlayer uses module augmentation to provide full TypeScript intellisense for yo
 }
 ```
 
----
-
 ## Git Configuration
 
 Add Intlayer's generated directory to your `.gitignore`:
@@ -345,8 +321,6 @@ Add Intlayer's generated directory to your `.gitignore`:
 .intlayer
 ```
 
----
-
 ## Go Further
 
 - **Visual Editor** — Manage translations visually in your browser: [Intlayer Visual Editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md)

package/docs/en/packages/@intlayer_babel/export.md

@@ -43,8 +43,6 @@ Import:
 import { ... } from "@intlayer/babel";
 ```
 
----
-
 ### Plugins
 
 | Function / Class               | Description                                                                                                                                                                                 |
@@ -57,8 +55,6 @@ import { ... } from "@intlayer/babel";
 | `makeUsageAnalyzerBabelPlugin` | Factory function that produces a Babel plugin to analyze the usage of `useIntlayer` / `getIntlayer` in the source code and aggregate field usage data in the shared `PruneContext`.         |
 | `getSharedPruneContext`        | Helper function that returns the shared `PruneContext` object for the specified base directory, or `null` if it has not been initialized yet.                                               |
 
----
-
 ### Plugin Configuration Utilities
 
 | Function                   | Description                                                                                                                                       |
@@ -68,8 +64,6 @@ import { ... } from "@intlayer/babel";
 | `getPurgePluginOptions`    | Loads the Intlayer configuration and returns `PurgePluginOptions` ready for use with `intlayerPurgeBabelPlugin`.                                  |
 | `getMinifyPluginOptions`   | Loads the Intlayer configuration and returns `MinifyPluginOptions` ready for use with `intlayerMinifyBabelPlugin`.                                |
 
----
-
 ### Types
 
 | Type                    | Description                                                                                                     |
@@ -87,8 +81,6 @@ import { ... } from "@intlayer/babel";
 | `CompatCallerConfig`    | Configuration for a compatible usage analyzer for compat-adapter packages (caller name and processing options). |
 | `ScriptBlock`           | Script block extracted from a SFC file (Vue or Svelte): content, start offset, and end offset.                  |
 
----
-
 ### Utility Functions
 
 | Function                          | Description                                                                                                                                                   |
@@ -100,8 +92,6 @@ import { ... } from "@intlayer/babel";
 | `BABEL_PARSER_OPTIONS`            | Constant representing Babel parser options covering the supported frameworks (React/Vue/Svelte/Angular/...).                                                  |
 | `INTLAYER_CALLER_NAMES`           | Constant list of original Intlayer caller names: `['useIntlayer', 'getIntlayer']`.                                                                            |
 
----
-
 ## Example Usage
 
 ```js

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

@@ -27,14 +27,10 @@ author: aymericzip
 
 The `t` function in the `adonis-intlayer` package is the core utility for providing localized responses in your AdonisJS application. It simplifies internationalization (i18n) by dynamically selecting content based on the user's preferred language.
 
----
-
 ## Overview
 
 The `t` function is used to define and retrieve translations for a given set of languages. It automatically determines the appropriate language to return based on the client's request settings, such as the `Accept-Language` header. If the preferred language is unavailable, it gracefully falls back to the default locale specified in your configuration.
 
----
-
 ## Key Features
 
 - **Dynamic Localization**: Automatically selects the most appropriate translation for the client.
@@ -42,8 +38,6 @@ The `t` function is used to define and retrieve translations for a given set of
 - **Asynchronous Context**: Works seamlessly within the AdonisJS request lifecycle using Async Local Storage.
 - **TypeScript Support**: Enforce type safety for your translations.
 
----
-
 ## Function Signature
 
 ```typescript
@@ -58,8 +52,6 @@ t(translations: Record<string, any>): any;
 
 - The content representing the client's preferred language.
 
----
-
 ## Loading the Middleware
 
 To ensure that the `t` function works correctly, you **must** register the `intlayer` middleware in your AdonisJS application.
@@ -68,8 +60,6 @@ To ensure that the `t` function works correctly, you **must** register the `intl
 router.use([() => import("adonis-intlayer/middleware")]);
 ```
 
----
-
 ## Usage Examples
 
 ### Basic Example
@@ -105,8 +95,6 @@ export default class ExampleController {
 }
 ```
 
----
-
 ## Advanced Topics
 
 ### Fallback Mechanism

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

@@ -28,14 +28,10 @@ author: aymericzip
 
 The `t` function in the `express-intlayer` package is the core utility for providing localized responses in your Express application. It simplifies internationalization (i18n) by dynamically selecting content based on the user's preferred language.
 
----
-
 ## Overview
 
 The `t` function is used to define and retrieve translations for a given set of languages. It automatically determines the appropriate language to return based on the client's request settings, such as the `Accept-Language` header. If the preferred language is unavailable, it gracefully falls back to the default locale specified in your configuration.
 
----
-
 ## Key Features
 
 - **Dynamic Localization**: Automatically selects the most appropriate translation for the client.
@@ -43,8 +39,6 @@ The `t` function is used to define and retrieve translations for a given set of
 - **Lightweight and Fast**: Designed for high-performance applications, ensuring minimal overhead.
 - **Strict Mode Support**: Enforce strict adherence to declared locales for reliable behavior.
 
----
-
 ## Function Signature
 
 ```typescript
@@ -59,8 +53,6 @@ t(translations: Record<string, string>): string;
 
 - A string representing the content in the client's preferred language.
 
----
-
 ## Loading the Internationalization Request Handler
 
 To ensure that the internationalization functionality provided by `express-intlayer` works correctly, you **must** load the internationalization middleware at the beginning of your Express application. This enables the `t` function and ensures proper handling of locale detection and translation.
@@ -94,8 +86,6 @@ app.get("/", (_req, res) => {
 - **Translation Context**: Sets up the necessary context for the `t` function to operate correctly, ensuring that translations are returned in the correct language.
 - **Error Prevention**: Without this middleware, using the `t` function will result in runtime errors because the necessary locale information won't be available.
 
----
-
 ## Usage Examples
 
 ### Basic Example
@@ -136,8 +126,6 @@ app.get("/error", (_req, res) => {
 });
 ```
 
----
-
 ### Using Locale Variants
 
 Specify translations for locale-specific variants:
@@ -184,8 +172,6 @@ app.get("/greet", (_req, res) => {
 });
 ```
 
----
-
 ## Advanced Topics
 
 ### Fallback Mechanism
@@ -210,8 +196,6 @@ For example:
 - If `defaultLocale` is `Locales.CHINESE` and a client requests `Locales.DUTCH`, the returned translation will default to the `Locales.CHINESE` value.
 - If `defaultLocale` is not defined, the `t` function will fallback to the `Locales.ENGLISH` value.
 
----
-
 ### Strict Mode Enforcement
 
 Configure the `t` function to enforce strict adherence to declared locales:
@@ -238,8 +222,6 @@ const config = {
 export default config;
 ```
 
----
-
 ### TypeScript Integration
 
 The `t` function is type-safe when used with TypeScript. Define a type-safe translations object:
@@ -258,8 +240,6 @@ app.get("/morning", (_req, res) => {
 });
 ```
 
----
-
 ### Common Errors and Troubleshooting
 
 | Issue                      | Cause                                   | Solution                                             |
@@ -267,8 +247,6 @@ app.get("/morning", (_req, res) => {
 | `t` function not working   | Middleware not loaded                   | Ensure `app.use(intlayer())` is added before routes. |
 | Missing translations error | Strict mode enabled without all locales | Provide all required translations.                   |
 
----
-
 ## Tips for Effective Usage
 
 1. **Centralize Translations**: Use a centralized module or JSON files for managing translations to improve maintainability.
@@ -276,8 +254,6 @@ app.get("/morning", (_req, res) => {
 3. **Combine with Frontend i18n**: Synchronize with frontend internationalization for a seamless user experience across the app.
 4. **Benchmark Performance**: Test your app's response times when adding translations to ensure minimal impact.
 
----
-
 ## Conclusion
 
 The `t` function is a powerful tool for backend internationalization. By using it effectively, you can create a more inclusive and user-friendly application for a global audience. For advanced usage and detailed configuration options, refer to the [documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md).

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

@@ -27,14 +27,10 @@ author: aymericzip
 
 The `t` function in the `hono-intlayer` package is the core utility for providing localized responses in your Hono application. It simplifies internationalization (i18n) by dynamically selecting content based on the user's preferred language.
 
----
-
 ## Overview
 
 The `t` function is used to define and retrieve translations for a given set of languages. It automatically determines the appropriate language to return based on the client's request settings, such as the `Accept-Language` header. If the preferred language is unavailable, it gracefully falls back to the default locale specified in your configuration.
 
----
-
 ## Key Features
 
 - **Dynamic Localization**: Automatically selects the most appropriate translation for the client.
@@ -42,8 +38,6 @@ The `t` function is used to define and retrieve translations for a given set of
 - **Lightweight and Fast**: Designed for high-performance applications, ensuring minimal overhead.
 - **Strict Mode Support**: Enforce strict adherence to declared locales for reliable behavior.
 
----
-
 ## Function Signature
 
 ```typescript
@@ -58,8 +52,6 @@ t(translations: Record<string, string>): string;
 
 - A string representing the content in the client's preferred language.
 
----
-
 ## Loading the Internationalization Request Handler
 
 To ensure that the internationalization functionality provided by `hono-intlayer` works correctly, you **must** load the internationalization middleware at the beginning of your Hono application. This enables the `t` function and ensures proper handling of locale detection and translation.
@@ -93,8 +85,6 @@ app.get("/", (c) => {
 - **Translation Context**: Sets up the necessary context for the `t` function to operate correctly, ensuring that translations are returned in the correct language.
 - **Error Prevention**: Without this middleware, using the `t` function will result in runtime errors because the necessary locale information won't be available.
 
----
-
 ## Usage Examples
 
 ### Basic Example
@@ -136,8 +126,6 @@ app.get("/error", (c) => {
 });
 ```
 
----
-
 ### Using Locale Variants
 
 Specify translations for locale-specific variants:
@@ -156,8 +144,6 @@ app.get("/greet", (c) => {
 });
 ```
 
----
-
 ## Advanced Topics
 
 ### Fallback Mechanism
@@ -177,8 +163,6 @@ const config = {
 export default config;
 ```
 
----
-
 ### Strict Mode Enforcement
 
 Configure the `t` function to enforce strict adherence to declared locales:
@@ -189,8 +173,6 @@ Configure the `t` function to enforce strict adherence to declared locales:
 | `inclusive` | Declared locales must have translations. Missing locales trigger warnings but are accepted. |
 | `loose`     | Any existing locale is accepted, even if not declared.                                      |
 
----
-
 ### TypeScript Integration
 
 The `t` function is type-safe when used with TypeScript. Define a type-safe translations object:
@@ -209,8 +191,6 @@ app.get("/morning", (c) => {
 });
 ```
 
----
-
 ### Common Errors and Troubleshooting
 
 | Issue                      | Cause                                   | Solution                                                  |
@@ -218,8 +198,6 @@ app.get("/morning", (c) => {
 | `t` function not working   | Middleware not loaded                   | Ensure `app.use("*", intlayer())` is added before routes. |
 | Missing translations error | Strict mode enabled without all locales | Provide all required translations.                        |
 
----
-
 ## Conclusion
 
 The `t` function is a powerful tool for backend internationalization. By using it effectively, you can create a more inclusive and user-friendly application for a global audience. For advanced usage and detailed configuration options, refer to the [documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md).

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

@@ -45,8 +45,6 @@ The package also exports the underlying [`normalizePath`](#normalizepath) helper
 - Tolerates missing leading slashes and empty values (normalized to `/`)
 - Lightweight — built on top of `getPathWithoutLocale`
 
----
-
 ## Function Signature
 
 ```typescript
@@ -62,8 +60,6 @@ normalizePath(
 ): string
 ```
 
----
-
 ## Parameters
 
 - `pathname: string`
@@ -86,8 +82,6 @@ normalizePath(
 - **Type**: `boolean`
 - **Description**: `true` when both inputs resolve to the same locale-agnostic path, otherwise `false`.
 
----
-
 ## Example Usage
 
 ### Basic Usage
@@ -132,8 +126,6 @@ const NavLink = ({ href, children }) => {
 };
 ```
 
----
-
 ## normalizePath
 
 `normalizePath` returns the canonical, locale-agnostic pathname used by `comparePaths`. It strips the locale segment, the protocol/host, the query string and the hash, ensures a single leading slash, removes any trailing slash (except for the root) and falls back to `/` for empty values.
@@ -150,16 +142,12 @@ normalizePath(""); // "/"
 normalizePath("https://example.com/ru/path"); // "/path"
 ```
 
----
-
 ## Related Functions
 
 - [`getPathWithoutLocale`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getPathWithoutLocale.md): Removes the locale segment from a URL or pathname.
 - [`getPrefix`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getPrefix.md): Determines the URL prefix for a given locale.
 - [`getLocalizedUrl`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getLocalizedUrl.md): Generates a localized URL for a specific locale.
 
----
-
 ## TypeScript
 
 ```typescript

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

@@ -37,8 +37,6 @@ The `getCanonicalPath` function resolves a localized URL path (e.g., `/a-propos`
 - Matches localized paths against custom rewrite rules defined in your configuration.
 - Returns the original path if no matching rewrite rule is found.
 
----
-
 ## Function Signature
 
 ```typescript
@@ -49,8 +47,6 @@ getCanonicalPath(
 ): string
 ```
 
----
-
 ## Parameters
 
 ### Required Parameters
@@ -72,15 +68,11 @@ getCanonicalPath(
   - **Type**: `RoutingConfig['rewrite']`
   - **Default**: `configuration.routing.rewrite`
 
----
-
 ## Returns
 
 - **Type**: `string`
 - **Description**: The internal canonical path.
 
----
-
 ## Example Usage
 
 ### Basic Usage (With Configuration)
@@ -126,8 +118,6 @@ getCanonicalPath("/contactez-nous", Locales.FRENCH, manualRules);
 // Output: "/contact"
 ```
 
----
-
 ## Related Functions
 
 - [`getLocalizedPath`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/packages/intlayer/getLocalizedPath.md): Resolves a canonical path into its localized equivalent.

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

@@ -31,8 +31,6 @@ author: aymericzip
 
 The `getConfiguration` function retrieves the entire configuration for the `intlayer` application by extracting environment variables. This function provides the flexibility to use the same configuration on both the client and server sides, ensuring consistency across the application.
 
----
-
 ## Parameters
 
 The function does not take any parameters. Instead, it uses environment variables for configuration.
@@ -48,8 +46,6 @@ The function does not take any parameters. Instead, it uses environment variable
 
 See [Intlayer configuration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md) for more details.
 
----
-
 ## Example Usage
 
 ### Retrieving the Full Configuration