@intlayer/docs 9.4.4 → 9.5.1

package/docs/en-GB/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 localised responses in your Express application. It simplifies internationalisation (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 Localisation**: 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**: Enforces strict adherence to declared locales for reliable behaviour.
 
----
-
 ## 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 Internationalisation Request Handler
 
 To ensure that the internationalisation functionality provided by `express-intlayer` works correctly, you **must** load the internationalisation 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 fall back 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. **Centralise Translations**: Use a centralised module or JSON files for managing translations to improve maintainability.
@@ -276,8 +254,6 @@ app.get("/morning", (_req, res) => {
 3. **Combine with Frontend i18n**: Synchronise with frontend internationalisation 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 internationalisation. 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-GB/configuration.md).

package/docs/en-GB/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-GB/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-GB/packages/intlayer/getPathWithoutLocale.md): Removes the locale segment from a URL or pathname.
 - [`getPrefix`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getPrefix.md): Determines the URL prefix for a given locale.
 - [`getLocalizedUrl`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getLocalizedUrl.md): Generates a localized URL for a specific locale.
 
----
-
 ## TypeScript
 
 ```typescript

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

@@ -37,8 +37,6 @@ The `getCanonicalPath` function resolves a localised URL path (e.g., `/a-propos`
 - Matches localised 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-GB/packages/intlayer/getLocalizedPath.md): Resolves a canonical path into its localised equivalent.

package/docs/en-GB/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-GB/configuration.md) for more details.
 
----
-
 ## Example Usage
 
 ### Retrieving the Full Configuration

package/docs/en-GB/packages/intlayer/getDictionary.md

@@ -41,8 +41,6 @@ Unlike [`getIntlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/doc
 - Fully typed: the returned object mirrors the `content` you passed
 - Accepts custom interpreter plugins
 
----
-
 ## Function Signature
 
 ```typescript
@@ -53,8 +51,6 @@ getDictionary(
 ): DeepTransformContent<...>
 ```
 
----
-
 ## Parameters
 
 - `dictionary: Dictionary | QualifiedDictionaryGroup`
@@ -77,8 +73,6 @@ getDictionary(
 - **Type**: The interpreted content of the dictionary.
 - **Description**: The `content` you passed, with every Intlayer node resolved for the requested locale. For a collection group without an `item` selector, an ordered array of interpreted entries is returned; `null` is returned when the selector targets nothing.
 
----
-
 ## Example Usage
 
 ### Basic Usage
@@ -126,16 +120,12 @@ const secondItem = getDictionary(blogPostGroup, { item: 2, locale: "fr" });
 const allItems = getDictionary(blogPostGroup, { locale: "fr" });
 ```
 
----
-
 ## Related Functions
 
 - [`getIntlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getIntlayer.md): Same interpretation, but the dictionary is looked up by key in the generated registry.
 - [`getDictionaryAsync`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getDictionaryAsync.md): Counterpart for per-locale loader maps.
 - [`useDictionary`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/react-intlayer/useDictionary.md): The React hook equivalent, reading the locale from the provider.
 
----
-
 ## TypeScript
 
 ```typescript

package/docs/en-GB/packages/intlayer/getDictionaryAsync.md

@@ -44,8 +44,6 @@ It is the counterpart of [`getDictionary`](https://github.com/aymericzip/intlaye
 - Deduplicates concurrent loads of the same chunk, and caches the resolved content
 - Failed loads are evicted from the cache so a later call retries the chunk
 
----
-
 ## Function Signature
 
 ```typescript
@@ -57,8 +55,6 @@ getDictionaryAsync(
 ): Promise<DeepTransformContent<...>>
 ```
 
----
-
 ## Parameters
 
 - `dictionaryLoaders: PlainDynamicLoaderMap | QualifiedDynamicLoaderMap`
@@ -86,8 +82,6 @@ getDictionaryAsync(
 - **Type**: `Promise<Content>` — a promise resolving to the interpreted content of the loaded chunk.
 - **Description**: Resolves to `null` when the map emits no chunk for the requested locale nor for any of its fallbacks, mirroring how a missing qualified coordinate resolves.
 
----
-
 ## Example Usage
 
 ### With a generated loader map
@@ -123,8 +117,6 @@ const promoBanner = await getDictionaryAsync(bannerLoaderMap, "banner", {
 });
 ```
 
----
-
 ## Behaviour Notes
 
 ### Caching and deduplication
@@ -135,16 +127,12 @@ The cache stores the **promise** of each `key + locale + selector` triple, so co
 
 A plain loader map is walked along the same fallback chain as the synchronous mode: the requested locale first, then its fallbacks, then `null` if none emitted a chunk.
 
----
-
 ## Related Functions
 
 - [`getIntlayerAsync`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getIntlayerAsync.md): The function applications call; build plugins rewrite it into `getDictionaryAsync`.
 - [`getDictionary`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getDictionary.md): Synchronous counterpart taking a full dictionary.
 - [Dynamic dictionaries](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/dynamic_dictionaries/index.md): Collections and variants, and the loader maps they generate.
 
----
-
 ## TypeScript
 
 ```typescript

package/docs/en-GB/packages/intlayer/getIntlayer.md

@@ -42,8 +42,6 @@ It reads the dictionaries generated by Intlayer in `.intlayer/`, so the `key` ar
 - Results are memoized per `key + locale + selector`
 - Falls back to a safe proxy in development when a dictionary is missing, instead of crashing
 
----
-
 ## Function Signature
 
 ```typescript
@@ -54,8 +52,6 @@ getIntlayer(
 ): DeepTransformContent<...>
 ```
 
----
-
 ## Parameters
 
 - `key: DictionaryKeys`
@@ -83,8 +79,6 @@ getIntlayer(
 - **Type**: The interpreted content of the dictionary, typed from your declaration.
 - **Description**: A plain object mirroring the `content` field of your dictionary, where every Intlayer node has been resolved to its final value for the requested locale.
 
----
-
 ## Example Usage
 
 ### Basic Usage
@@ -152,8 +146,6 @@ const allPosts = getIntlayer("blog-post", { locale: "fr" });
 const banner = getIntlayer("banner", { variant: "black-friday", locale: "fr" });
 ```
 
----
-
 ## Behaviour Notes
 
 ### Caching
@@ -168,16 +160,12 @@ In development, requesting a key that has no generated dictionary logs a warning
 
 `getIntlayer` reads the merged dictionary, which holds **every** locale. In client bundles, the [build plugins](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/bundle_optimization.md) rewrite the call so only the required content is shipped. When you read content outside of rendering (metadata, loaders, server functions) and want a single locale loaded on demand, use [`getIntlayerAsync`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getIntlayerAsync.md) instead.
 
----
-
 ## Related Functions
 
 - [`getIntlayerAsync`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getIntlayerAsync.md): Async counterpart loading a single locale chunk.
 - [`getDictionary`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getDictionary.md): Interprets a dictionary object you pass yourself, instead of one looked up by key.
 - [`useIntlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/react-intlayer/useIntlayer.md): The React hook equivalent, reading the locale from the provider.
 
----
-
 ## TypeScript
 
 ```typescript

package/docs/en-GB/packages/intlayer/getIntlayerAsync.md

@@ -46,8 +46,6 @@ Without those plugins — an unoptimised build — the call resolves through the
 - Concurrent calls for the same chunk share a single load
 - Safe to use in `async` metadata builders, loaders and server functions
 
----
-
 ## Function Signature
 
 ```typescript
@@ -58,8 +56,6 @@ getIntlayerAsync(
 ): Promise<DeepTransformContent<...>>
 ```
 
----
-
 ## Parameters
 
 - `key: DictionaryKeys`
@@ -86,8 +82,6 @@ getIntlayerAsync(
 
 - **Type**: `Promise<Content>` — a promise resolving to the interpreted content of the dictionary, typed from your declaration.
 
----
-
 ## Example Usage
 
 ### Basic Usage
@@ -98,8 +92,6 @@ import { getIntlayerAsync } from "intlayer";
 const { title } = await getIntlayerAsync("app", "fr"); // "Bonjour"
 ```
 
----
-
 ## `getIntlayer` vs `getIntlayerAsync`
 
 |                    | [`getIntlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getIntlayer.md) | `getIntlayerAsync`                                |
@@ -111,16 +103,12 @@ const { title } = await getIntlayerAsync("app", "fr"); // "Bonjour"
 
 Both accept the same arguments and return the same content: switching from one to the other only changes **when** and **how much** is loaded.
 
----
-
 ## Related Functions
 
 - [`getIntlayer`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getIntlayer.md): Synchronous equivalent reading the merged dictionary.
 - [`getDictionaryAsync`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getDictionaryAsync.md): The lower-level function the build plugins rewrite this call into.
 - [`getLocale`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getLocale.md): Detects the locale of an incoming request.
 
----
-
 ## TypeScript
 
 ```typescript

package/docs/en-GB/packages/intlayer/getLocalizedPath.md

@@ -39,8 +39,6 @@ It is the relative counterpart of [`getLocalizedUrl`](https://github.com/aymeric
 - Resolves paths according to custom rewrite rules defined in your configuration.
 - Automatically handles fallback to the canonical path if no rewrite rule is found for the specified locale.
 
----
-
 ## Function Signature
 
 ```typescript
@@ -51,8 +49,6 @@ getLocalizedPath(
 ): string
 ```
 
----
-
 ## Parameters
 
 ### Required Parameters
@@ -79,8 +75,6 @@ getLocalizedPath(
   - `options.mode?: 'prefix-no-default' | 'prefix-all' | 'no-prefix' | 'search-params'` — how the locale appears in the path. **Default**: `configuration.routing.mode`
   - `options.rewrite?: RoutingConfig['rewrite']` — custom rewrite rules. **Default**: `configuration.routing.rewrite`
 
----
-
 ## Returns
 
 - **Type**: `string`
@@ -108,8 +102,6 @@ Two cases stay widened to `string`, because they cannot be resolved at compile t
 - a path that is not a string literal (e.g. one built from a variable);
 - a path matched by a rule using a multi-segment or optional parameter (`[...slug]`, `[[...slug]]`, `:param?`).
 
----
-
 ## Example Usage
 
 ### Basic Usage (With Configuration)
@@ -167,8 +159,6 @@ getLocalizedPath("/about");
 // Output: "/about"
 ```
 
----
-
 ## Related Functions
 
 - [`getCanonicalPath`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getCanonicalPath.md): Resolves a localised path back to its internal canonical path.

package/docs/en-GB/packages/intlayer/getLocalizedUrl.md

@@ -39,8 +39,6 @@ The `getLocalizedUrl` function generates a localised URL by prefixing the given
 - Can be used with minimal parameters for simple cases or fully customised for complex scenarios
 - Supports multiple routing modes: `prefix-no-default`, `prefix-all`, `no-prefix`, and `search-params`
 
----
-
 ## Function Signature
 
 ```typescript
@@ -55,8 +53,6 @@ getLocalizedUrl(
 ): string
 ```
 
----
-
 ## Parameters
 
 ### Required Parameters
@@ -103,8 +99,6 @@ getLocalizedUrl(
 - **Type**: `string`
 - **Description**: The localised URL for the specified locale.
 
----
-
 ## Example Usage
 
 ### Basic Usage (Only Required Parameters)
@@ -206,8 +200,6 @@ getLocalizedUrl(
 ); // Output: "/about" (no prefix applied for unsupported locale)
 ```
 
----
-
 ## Edge Cases
 
 - **No Locale Segment:**
@@ -225,8 +217,6 @@ getLocalizedUrl(
   - `'no-prefix'`: No locale prefixes in URLs (locale handled elsewhere)
   - `'search-params'`: Locale specified via query parameter (e.g., `/about?locale=fr`)
 
----
-
 ## Usage in Applications
 
 In a multilingual application, configuring the internationalisation settings with `locales` and `defaultLocale` is critical for ensuring the correct language is displayed. Below is an example of how `getLocalizedUrl` can be used in an application setup:

package/docs/en-GB/packages/intlayer/getMultilingualUrls.md

@@ -39,8 +39,6 @@ The `getMultilingualUrls` function generates a mapping of multilingual URLs by p
 - Supports multiple routing modes: `prefix-no-default`, `prefix-all`, `no-prefix`, and `search-params`
 - Returns a mapping object with all locales as keys and their corresponding URLs as values
 
----
-
 ## Function Signature
 
 ```typescript
@@ -54,8 +52,6 @@ getMultilingualUrls(
 ): StrictModeLocaleMap<string>
 ```
 
----
-
 ## Parameters
 
 ### Required Parameters
@@ -97,8 +93,6 @@ getMultilingualUrls(
 - **Type**: `IConfigLocales<string>`
 - **Description**: An object mapping each locale to its corresponding multilingual URL.
 
----
-
 ## Example Usage
 
 ### Basic Usage (Uses Project Configuration)
@@ -162,8 +156,6 @@ getMultilingualUrls(
 // }
 ```
 
----
-
 ## Edge Cases
 
 - **No Locale Segment:**
@@ -181,8 +173,6 @@ getMultilingualUrls(
   - `'no-prefix'`: No locale prefixes in URLs (all locales return same URL)
   - `'search-params'`: Locale specified via query parameter (e.g., `/dashboard?locale=fr`)
 
----
-
 ## Usage in Applications
 
 In a multilingual application, configuring the internationalisation settings with `locales` and `defaultLocale` is critical for ensuring the correct language is displayed. Below is an example of how `getMultilingualUrls` can be used in an application setup:

package/docs/en-GB/packages/intlayer/getPrefix.md

@@ -39,8 +39,6 @@ The `getPrefix` function determines the URL prefix for a given locale based on t
 - Supports all routing modes: `prefix-no-default`, `prefix-all`, `no-prefix`, and `search-params`
 - Lightweight utility for determining when to add locale prefixes
 
----
-
 ## Function Signature
 
 ```typescript
@@ -58,8 +56,6 @@ type GetPrefixResult = {
 }
 ```
 
----
-
 ## Parameters
 
 - `locale: Locales`
@@ -94,8 +90,6 @@ type GetPrefixResult = {
   - `prefix`: The path prefix with trailing slash (e.g., `'fr/'`, `''`)
   - `localePrefix`: The locale identifier without slashes (e.g., `'fr'`, `undefined`)
 
----
-
 ## Example Usage
 
 ### Basic Usage
@@ -173,15 +167,11 @@ console.log(`Current locale: ${localePrefix}`);
 // Output: "Current locale: fr"
 ```
 
----
-
 ## Related Functions
 
 - [`getLocalizedUrl`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getLocalizedUrl.md): Generates a localised URL for a specific locale
 - [`getMultilingualUrls`](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en-GB/packages/intlayer/getMultilingualUrls.md): Generates URLs for all configured locales
 
----
-
 ## TypeScript
 
 ```typescript