@intlayer/docs 8.2.2 → 8.2.4

package/docs/ar/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - يُستخدم **`IntlayerClientProvider`** لتوفير اللغة للأبناء في جانب العميل.
 - بينما يُستخدم **`IntlayerServerProvider`** لتوفير اللغة للأبناء في جانب الخادم.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (اختياري) الخطوة 7: ملء الترجمات المفقودة
 
 يوفر Intlayer أداة CLI لمساعدتك في ملء الترجمات المفقودة. يمكنك استخدام الأمر `intlayer` لاختبار وملء الترجمات المفقودة من التعليمات البرمجية الخاصة بك.

package/docs/ar/intlayer_with_nextjs_no_locale_path.md

@@ -728,6 +728,7 @@ const Page: NextPage = async () => {
 
   > لا يمكن أن يتشارك الـ layout والصفحة نفس سياق الخادم لأن نظام سياق الخادم يعتمد على مخزن بيانات لكل طلب (عبر آلية [React's cache](https://react.dev/reference/react/cache))، مما يجعل كل "context" يُعاد إنشاؤه لأجزاء مختلفة من التطبيق. وضع الـ provider في layout مشترك سيكسر هذا العزل، وسيمنع الانتشار الصحيح لقيم سياق الخادم إلى مكوناتك على الخادم.
 
+
 ```tsx {4,7} fileName="src/components/clientComponentExample/ClientComponentExample.tsx" codeFormat="typescript"
 "use client";
 

package/docs/ar/per_locale_file.md

@@ -128,7 +128,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-باستخدام هذا التكوين، سيتم إنشاء جميع ملفات كل لغة مع تعيين اللغة الافتراضية إلى الإنجليزية. يتضمن ذلك أيضاً إنشاء ملفات `.content` باستخدام أمر `extract` والمترجم (compiler). (انظر [Compiler](https://intlayer.org/doc/compiler) أو [Extract](https://intlayer.org/doc/concept/cli/extract) لمزيد من المعلومات.)
+باستخدام هذا التكوين، سيتم إنشاء جميع ملفات كل لغة مع تعيين اللغة الافتراضية إلى الإنجليزية. يتضمن ذلك أيضاً إنشاء ملفات `.content` باستخدام أمر `extract` والمترجم (compiler). (انظر [Compiler](https://intlayer.org/doc/compiler) أو [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md) لمزيد من المعلومات.)
 
 ## تنسيق حسب اللغة
 

package/docs/de/intlayer_with_nextjs_16.md

@@ -636,7 +636,7 @@ const Page = async ({ params }) => {
 
   > Layout und Seite können keinen gemeinsamen Server-Kontext teilen, da das Server-Kontext-System auf einem pro-Anfrage-Datenspeicher basiert (über den [React Cache](https://react.dev/reference/react/cache)-Mechanismus), wodurch jeder "Kontext" für verschiedene Segmente der Anwendung neu erstellt wird. Das Platzieren des Providers in einem gemeinsamen Layout würde diese Isolation aufheben und verhindern, dass die Server-Kontextwerte korrekt an Ihre Server-Komponenten weitergegeben werden.
 
-> Layout und Seite können keinen gemeinsamen Server-Kontext teilen, da das Server-Kontext-System auf einem pro-Anfrage-Datenspeicher basiert (über den [React-Cache](https://react.dev/reference/react/cache)-Mechanismus), wodurch jeder "Kontext" für verschiedene Segmente der Anwendung neu erstellt wird. Das Platzieren des Providers in einem gemeinsamen Layout würde diese Isolation aufheben und die korrekte Weitergabe der Server-Kontextwerte an Ihre Server-Komponenten verhindern.
+  > Layout und Seite können keinen gemeinsamen Server-Kontext teilen, da das Server-Kontext-System auf einem pro-Anfrage-Datenspeicher basiert (über den [React-Cache](https://react.dev/reference/react/cache)-Mechanismus), wodurch jeder "Kontext" für verschiedene Segmente der Anwendung neu erstellt wird. Das Platzieren des Providers in einem gemeinsamen Layout würde diese Isolation aufheben und die korrekte Weitergabe der Server-Kontextwerte an Ihre Server-Komponenten verhindern.
 
 ```tsx {4,7} fileName="src/components/ClientComponentExample.tsx" codeFormat="typescript"
 "use client";

package/docs/de/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** wird verwendet, um die Sprache für Client-Komponenten bereitzustellen.
 - **`IntlayerServerProvider`** wird verwendet, um die Sprache für Server-Kinder bereitzustellen.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Optional) Schritt 7: Fehlende Übersetzungen ausfüllen
 
 Intlayer bietet ein CLI-Tool an, um fehlende Übersetzungen auszufüllen. Sie können den Befehl `intlayer` verwenden, um fehlende Übersetzungen in Ihrem Code zu testen und auszufüllen.

package/docs/de/per_locale_file.md

@@ -128,7 +128,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-Mit dieser Konfiguration werden alle Per-Locale-Dateien mit der Standard-Locale Englisch generiert. Dies beinhaltet auch die Generierung von `.content`-Dateien unter Verwendung des `extract`-Befehls und des Compilers. (Siehe [Compiler](https://intlayer.org/doc/compiler) oder [Extract](https://intlayer.org/doc/concept/cli/extract) für weitere Informationen.)
+Mit dieser Konfiguration werden alle Per-Locale-Dateien mit der Standard-Locale Englisch generiert. Dies beinhaltet auch die Generierung von `.content`-Dateien unter Verwendung des `extract`-Befehls und des Compilers. (Siehe [Compiler](https://intlayer.org/doc/compiler) oder [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md) für weitere Informationen.)
 
 ## Pro-Locale-Format
 

package/docs/en/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** is used to provide the locale to client-side components.
 - **`IntlayerServerProvider`** is used to provide the locale to the server children.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Optional) Step 7: Fill missing translation
 
 Intlayer provide a CLI tool to help you fill missing translations. You can use the `intlayer` command to test and fill missing translations from your code.

package/docs/en/per_locale_file.md

@@ -167,7 +167,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-Using this configuration, all per-locale files will be generated with the default locale set to English. It also include generation of `.content` files using the `extract` command, and the compiler. (See [Compiler](https://intlayer.org/doc/compiler) or [Extract](https://intlayer.org/doc/concept/cli/extract) for more information.)
+Using this configuration, all per-locale files will be generated with the default locale set to English. It also include generation of `.content` files using the `extract` command, and the compiler. (See [Compiler](https://intlayer.org/doc/compiler) or [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md) for more information.)
 
 ## Single File with Multiple Translations
 

package/docs/en-GB/intlayer_with_nextjs_compiler.md

@@ -321,6 +321,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** is used to provide the locale to client-side components.
 - **`IntlayerServerProvider`** is used to provide the locale to the server children.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Optional) Step 7: Fill missing translation
 
 Intlayer provide a CLI tool to help you fill missing translations. You can use the `intlayer` command to test and fill missing translations from your code.

package/docs/en-GB/per_locale_file.md

@@ -126,7 +126,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-Using this configuration, all per-locale files will be generated with the default locale set to English. It also includes generation of `.content` files using the `extract` command, and the compiler. (See [Compiler](https://intlayer.org/doc/compiler) or [Extract](https://intlayer.org/doc/concept/cli/extract) for more information.)
+Using this configuration, all per-locale files will be generated with the default locale set to English. It also includes generation of `.content` files using the `extract` command, and the compiler. (See [Compiler](https://intlayer.org/doc/compiler) or [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md) for more information.)
 
 ## Per-Locale Format
 

package/docs/es/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** se utiliza para proporcionar el locale a los componentes del lado del cliente.
 - **`IntlayerServerProvider`** se utiliza para proporcionar el locale a los hijos del servidor.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Opcional) Paso 7: Completar traducciones faltantes
 
 Intlayer proporciona una herramienta CLI para ayudarle a completar las traducciones faltantes. Puede utilizar el comando `intlayer` para probar y completar las traducciones faltantes de su código.

package/docs/fr/intlayer_with_nextjs_15.md

@@ -551,7 +551,7 @@ const Page = async ({ params }) => {
 
   > Le layout et la page ne peuvent pas partager un contexte serveur commun car le système de contexte serveur est basé sur un magasin de données par requête (via le mécanisme [cache de React](https://react.dev/reference/react/cache)), ce qui fait que chaque "contexte" est recréé pour différents segments de l'application. Placer le provider dans un layout partagé casserait cette isolation, empêchant la bonne propagation des valeurs du contexte serveur à vos composants serveur.
 
-> La mise en page (layout) et la page ne peuvent pas partager un contexte serveur commun car le système de contexte serveur est basé sur un magasin de données par requête (via le mécanisme [React's cache](https://react.dev/reference/react/cache)), ce qui entraîne la recréation de chaque "contexte" pour différents segments de l'application. Placer le provider dans une mise en page partagée briserait cette isolation, empêchant la bonne propagation des valeurs du contexte serveur à vos composants serveur.
+  > La mise en page (layout) et la page ne peuvent pas partager un contexte serveur commun car le système de contexte serveur est basé sur un magasin de données par requête (via le mécanisme [React's cache](https://react.dev/reference/react/cache)), ce qui entraîne la recréation de chaque "contexte" pour différents segments de l'application. Placer le provider dans une mise en page partagée briserait cette isolation, empêchant la bonne propagation des valeurs du contexte serveur à vos composants serveur.
 
 ```tsx {4,7} fileName="src/components/ClientComponentExample.tsx" codeFormat="typescript"
 "use client";

package/docs/fr/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** est utilisé pour fournir la locale aux composants côté client.
 - **`IntlayerServerProvider`** est utilisé pour fournir la locale aux enfants serveurs.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Optionnel) Étape 7 : Remplir les traductions manquantes
 
 Intlayer fournit un outil CLI pour vous aider à remplir les traductions manquantes. Vous pouvez utiliser la commande `intlayer` pour tester et remplir les traductions manquantes de votre code.

package/docs/hi/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** का उपयोग क्लाइंट साइड पर बच्चों को लोकेल प्रदान करने के लिए किया जाता है।
 - जबकि **`IntlayerServerProvider`** का उपयोग सर्वर साइड पर बच्चों को लोकेल प्रदान करने के लिए किया जाता है।
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (वैकल्पिक) चरण 7: छूटे हुए अनुवाद भरें
 
 Intlayer छूटे हुए अनुवादों को भरने में आपकी मदद करने के लिए एक CLI टूल प्रदान करता है। आप अपने कोड से छूटे हुए अनुवादों का परीक्षण करने और उन्हें भरने के लिए `intlayer` कमांड का उपयोग कर सकते हैं।

package/docs/hi/per_locale_file.md

@@ -128,7 +128,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-इस कॉन्फ़िगरेशन का उपयोग करते हुए, सभी प्रति-लोकेल फ़ाइलें डिफ़ॉल्ट लोकेल को अंग्रेज़ी पर सेट करके जेनरेट की जाएंगी। इसमें `extract` कमांड और कंपाइलर का उपयोग करके `.content` फ़ाइलों का जनरेशन भी शामिल है। (अधिक जानकारी के लिए [Compiler](https://intlayer.org/doc/compiler) या [Extract](https://intlayer.org/doc/concept/cli/extract) देखें।)
+इस कॉन्फ़िगरेशन का उपयोग करते हुए, सभी प्रति-लोकेल फ़ाइलें डिफ़ॉल्ट लोकेल को अंग्रेज़ी पर सेट करके जेनरेट की जाएंगी। इसमें `extract` कमांड और कंपाइलर का उपयोग करके `.content` फ़ाइलों का जनरेशन भी शामिल है। (अधिक जानकारी के लिए [Compiler](https://intlayer.org/doc/compiler) या [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md) देखें।)
 
 ## प्रति-स्थान प्रारूप
 

package/docs/id/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** digunakan untuk menyediakan bahasa ke komponen sisi klien.
 - Sementara **`IntlayerServerProvider`** digunakan untuk menyediakan bahasa ke anak-anak server.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Opsional) Langkah 7: Isi terjemahan yang hilang
 
 Intlayer menyediakan alat CLI untuk membantu Anda mengisi terjemahan yang hilang. Anda dapat menggunakan perintah `intlayer` untuk menguji dan mengisi terjemahan yang hilang dari kode Anda.

package/docs/id/per_locale_file.md

@@ -128,7 +128,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-Dengan menggunakan konfigurasi ini, semua file per-locale akan dibuat dengan locale default yang diatur ke bahasa Inggris. Ini juga mencakup pembuatan file `.content` menggunakan perintah `extract`, dan compiler. (Lihat [Compiler](https://intlayer.org/doc/compiler) atau [Extract](https://intlayer.org/doc/concept/cli/extract) untuk informasi lebih lanjut.)
+Dengan menggunakan konfigurasi ini, semua file per-locale akan dibuat dengan locale default yang diatur ke bahasa Inggris. Ini juga mencakup pembuatan file `.content` menggunakan perintah `extract`, dan compiler. (Lihat [Compiler](https://intlayer.org/doc/compiler) atau [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md) untuk informasi lebih lanjut.)
 
 ## Format Per-Locale
 

package/docs/it/intlayer_with_nextjs_15.md

@@ -544,7 +544,7 @@ const Page = async ({ params }) => {
 
   > Layout e pagina non possono condividere un contesto server comune perché il sistema di contesto server si basa su un archivio dati per richiesta (tramite il meccanismo [React's cache](https://react.dev/reference/react/cache)), causando la ricreazione di ogni "contesto" per segmenti diversi dell'applicazione. Posizionare il provider in un layout condiviso romperebbe questa isolamento, impedendo la corretta propagazione dei valori del contesto server ai componenti server.
 
-> Layout e pagina non possono condividere un contesto server comune perché il sistema di contesto server si basa su un archivio dati per richiesta (tramite il meccanismo [React's cache](https://react.dev/reference/react/cache)), causando la ricreazione di ogni "contesto" per diversi segmenti dell'applicazione. Posizionare il provider in un layout condiviso romperebbe questa isolazione, impedendo la corretta propagazione dei valori del contesto server ai tuoi componenti server.
+  > Layout e pagina non possono condividere un contesto server comune perché il sistema di contesto server si basa su un archivio dati per richiesta (tramite il meccanismo [React's cache](https://react.dev/reference/react/cache)), causando la ricreazione di ogni "contesto" per diversi segmenti dell'applicazione. Posizionare il provider in un layout condiviso romperebbe questa isolazione, impedendo la corretta propagazione dei valori del contesto server ai tuoi componenti server.
 
 ```tsx {4,7} fileName="src/components/ClientComponentExample.tsx" codeFormat="typescript"
 "use client";

package/docs/it/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** serve per fornire la lingua ai componenti client.
 - **`IntlayerServerProvider`** serve per fornire la lingua ai componenti server figli.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Opzionale) Passo 7: Completare le traduzioni mancanti
 
 Intlayer offre uno strumento CLI per completare le traduzioni mancanti. Usa il comando `intlayer` per testare e riempire le lacune nel codice.

package/docs/it/per_locale_file.md

@@ -128,7 +128,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-Utilizzando questa configurazione, tutti i file per-locale verranno generati con la locale predefinita impostata su inglese. Include anche la generazione di file `.content` utilizzando il comando `extract` e il compilatore. (Vedere [Compilatore](https://intlayer.org/doc/compiler) o [Extract](https://intlayer.org/doc/concept/cli/extract) per ulteriori informazioni.)
+Utilizzando questa configurazione, tutti i file per-locale verranno generati con la locale predefinita impostata su inglese. Include anche la generazione di file `.content` utilizzando il comando `extract` e il compilatore. (Vedere [Compilatore](https://intlayer.org/doc/compiler) o [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md) per ulteriori informazioni.)
 
 ## Formato per Locale
 

package/docs/ja/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** は、クライアントサイドで子要素にロケールを提供するために使用されます。
 - 一方、 **`IntlayerServerProvider`** は、サーバーサイドで子要素にロケールを提供するために使用されます。
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (オプション) ステップ 7: 不足している翻訳を埋める
 
 Intlayerは、不足している翻訳を埋めるためのCLIツールを提供しています。 `intlayer` コマンドを使用して、コード内の不足している翻訳をテストして埋めることができます。

package/docs/ja/intlayer_with_nextjs_no_locale_path.md

@@ -772,6 +772,7 @@ const Page: NextPage = async () => {
 
   > Layout と page は共通の server context を共有できません。server context システムはリクエスト単位のデータストア（[React の cache](https://react.dev/reference/react/cache) 機構）に基づいており、アプリケーションの異なるセグメントごとに各 "context" が再作成されます。provider を共有 layout に配置するとこの分離が壊れ、server component に対する server context 値の正しい伝播が妨げられます。
 
+
 ```tsx {4,7} fileName="src/components/clientComponentExample/ClientComponentExample.tsx" codeFormat="typescript"
 "use client";
 

package/docs/ko/intlayer_with_nextjs_15.md

@@ -583,7 +583,7 @@ const Page = async ({ params }) => {
 
   > 레이아웃과 페이지는 공통 서버 컨텍스트를 공유할 수 없습니다. 서버 컨텍스트 시스템이 요청별 데이터 저장소([React의 cache](https://react.dev/reference/react/cache) 메커니즘)를 기반으로 하기 때문에 애플리케이션의 서로 다른 세그먼트마다 각 "컨텍스트"가 다시 생성됩니다. 공급자를 공유 레이아웃에 배치하면 이러한 격리가 깨져 서버 컴포넌트에 서버 컨텍스트 값이 올바르게 전파되지 않습니다.
 
-> 레이아웃과 페이지는 공통 서버 컨텍스트를 공유할 수 없습니다. 서버 컨텍스트 시스템이 요청별 데이터 저장소([React의 캐시](https://react.dev/reference/react/cache) 메커니즘)를 기반으로 하기 때문에 애플리케이션의 서로 다른 세그먼트마다 각 "컨텍스트"가 다시 생성됩니다. 제공자를 공유 레이아웃에 배치하면 이 격리가 깨져 서버 컨텍스트 값이 서버 컴포넌트에 올바르게 전달되지 않습니다.
+  > 레이아웃과 페이지는 공통 서버 컨텍스트를 공유할 수 없습니다. 서버 컨텍스트 시스템이 요청별 데이터 저장소([React의 캐시](https://react.dev/reference/react/cache) 메커니즘)를 기반으로 하기 때문에 애플리케이션의 서로 다른 세그먼트마다 각 "컨텍스트"가 다시 생성됩니다. 제공자를 공유 레이아웃에 배치하면 이 격리가 깨져 서버 컨텍스트 값이 서버 컴포넌트에 올바르게 전달되지 않습니다.
 
 ```tsx {4,7} fileName="src/components/ClientComponentExample.tsx" codeFormat="typescript"
 "use client";

package/docs/ko/intlayer_with_nextjs_compiler.md

@@ -321,6 +321,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`**는 클라이언트 측에서 자식 요소에 로캘을 제공하는 데 사용됩니다.
 - 반면 **`IntlayerServerProvider`**는 서버 측에서 자식 요소에 로캘을 제공하는 데 사용됩니다.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (선택 사항) 7단계: 누락된 번역 채우기
 
 Intlayer는 누락된 번역을 채울 수 있도록 CLI 도구를 제공합니다. `intlayer` 명령을 사용하여 코드에서 누락된 번역을 테스트하고 채울 수 있습니다.

package/docs/pl/intlayer_with_nextjs_15.md

@@ -617,7 +617,7 @@ const Page = async ({ params }) => {
 
   > Layout i strona nie mogą współdzielić wspólnego kontekstu serwera, ponieważ system kontekstu serwera opiera się na magazynie danych na żądanie (za pomocą mechanizmu [React's cache](https://react.dev/reference/react/cache)), co powoduje, że każdy "kontekst" jest tworzony na nowo dla różnych segmentów aplikacji. Umieszczenie providera w wspólnym layoucie złamałoby tę izolację, uniemożliwiając prawidłowe propagowanie wartości kontekstu serwera do komponentów serwerowych.
 
-> Layout i strona nie mogą współdzielić wspólnego kontekstu serwera, ponieważ system kontekstu serwera opiera się na magazynie danych na żądanie (za pomocą mechanizmu [React's cache](https://react.dev/reference/react/cache)), co powoduje, że każdy "kontekst" jest tworzony na nowo dla różnych segmentów aplikacji. Umieszczenie providera w współdzielonym layoucie złamałoby tę izolację, uniemożliwiając prawidłowe propagowanie wartości kontekstu serwera do komponentów serwerowych.
+  > Layout i strona nie mogą współdzielić wspólnego kontekstu serwera, ponieważ system kontekstu serwera opiera się na magazynie danych na żądanie (za pomocą mechanizmu [React's cache](https://react.dev/reference/react/cache)), co powoduje, że każdy "kontekst" jest tworzony na nowo dla różnych segmentów aplikacji. Umieszczenie providera w współdzielonym layoucie złamałoby tę izolację, uniemożliwiając prawidłowe propagowanie wartości kontekstu serwera do komponentów serwerowych.
 
 ```tsx {4,7} fileName="src/components/ClientComponentExample.tsx" codeFormat="typescript"
 "use client";

package/docs/pl/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** służy do dostarczania języka dzięcom po stronie klienta (Client Side).
 - **`IntlayerServerProvider`** służy do dostarczania języka dzięcom po stronie serwera (Server Side).
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Opcjonalnie) Krok 7: Uzupełnij brakujące tłumaczenia
 
 Intlayer udostępnia narzędzie CLI, które pomaga uzupełnić brakujące tłumaczenia. Możesz użyć polecenia `intlayer`, aby przetestować i uzupełnić brakujące tłumaczenia ze swojego kodu.

package/docs/pl/per_locale_file.md

@@ -126,7 +126,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-Korzystając z tej konfiguracji, wszystkie pliki dla poszczególnych lokali będą generowane z domyślnym lokalem ustawionym na angielski. Obejmuje to również generowanie plików `.content` za pomocą polecenia `extract` oraz kompilatora. (Zobacz [Compiler](https://intlayer.org/doc/compiler) lub [Extract](https://intlayer.org/doc/concept/cli/extract), aby uzyskać więcej informacji.)
+Korzystając z tej konfiguracji, wszystkie pliki dla poszczególnych lokali będą generowane z domyślnym lokalem ustawionym na angielski. Obejmuje to również generowanie plików `.content` za pomocą polecenia `extract` oraz kompilatora. (Zobacz [Compiler](https://intlayer.org/doc/compiler) lub [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md), aby uzyskać więcej informacji.)
 
 ## Format per-locale
 

package/docs/pt/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** é usado para fornecer o locale aos componentes do lado do cliente.
 - **`IntlayerServerProvider`** é usado para fornecer o locale aos filhos do servidor.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Opcional) Passo 7: Preencher traduções em falta
 
 O Intlayer fornece uma ferramenta CLI para ajudar a preencher traduções em falta. Pode usar o comando `intlayer` para testar e preencher as traduções em falta do seu código.

package/docs/pt/per_locale_file.md

@@ -128,7 +128,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-Usando essa configuração, todos os arquivos por localidade serão gerados com a localidade padrão definida como Inglês. Isso também inclui a geração de arquivos `.content` usando o comando `extract` e o compiler. (Veja [Compiler](https://intlayer.org/doc/compiler) ou [Extract](https://intlayer.org/doc/concept/cli/extract) para mais informações.)
+Usando essa configuração, todos os arquivos por localidade serão gerados com a localidade padrão definida como Inglês. Isso também inclui a geração de arquivos `.content` usando o comando `extract` e o compiler. (Veja [Compiler](https://intlayer.org/doc/compiler) ou [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md) para mais informações.)
 
 ## Formato Por Localidade
 

package/docs/ru/intlayer_with_nextjs_15.md

@@ -548,7 +548,7 @@ const Page = async ({ params }) => {
 
   > Layout и страница не могут использовать общий серверный контекст, потому что система серверного контекста основана на хранилище данных для каждого запроса (через механизм [React's cache](https://react.dev/reference/react/cache)), из-за чего каждый "контекст" создаётся заново для разных сегментов приложения. Размещение провайдера в общем layout нарушит эту изоляцию и помешает правильной передаче значений серверного контекста вашим серверным компонентам.
 
-> Макет и страница не могут использовать общий серверный контекст, поскольку система серверного контекста основана на хранилище данных для каждого запроса (через механизм [кэша React](https://react.dev/reference/react/cache)), из-за чего каждый "контекст" создаётся заново для разных сегментов приложения. Размещение провайдера в общем макете нарушит эту изоляцию, что помешает правильной передаче значений серверного контекста вашим серверным компонентам.
+  > Макет и страница не могут использовать общий серверный контекст, поскольку система серверного контекста основана на хранилище данных для каждого запроса (через механизм [кэша React](https://react.dev/reference/react/cache)), из-за чего каждый "контекст" создаётся заново для разных сегментов приложения. Размещение провайдера в общем макете нарушит эту изоляцию, что помешает правильной передаче значений серверного контекста вашим серверным компонентам.
 
 ```tsx {4,7} fileName="src/components/ClientComponentExample.tsx" codeFormat="typescript"
 "use client";

package/docs/ru/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** используется для предоставления языка компонентам на стороне клиента.
 - **`IntlayerServerProvider`** используется для предоставления языка дочерним элементам сервера.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Необязательно) Шаг 7: Заполнение недостающих переводов
 
 Intlayer предоставляет инструмент CLI, помогающий заполнить недостающие переводы. Вы можете использовать команду `intlayer` для проверки и заполнения недостающих переводов в вашем коде.

package/docs/tr/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`**, istemci tarafındaki bileşenlere dil sağlamak için kullanılır.
 - **`IntlayerServerProvider`** ise sunucu tarafındaki alt bileşenlere dil sağlamak için kullanılır.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (İsteğe bağlı) Adım 7: Eksik çevirileri doldurma
 
 Intlayer, eksik çevirileri doldurmanıza yardımcı olacak bir CLI aracı sağlar. Kodunuzdaki eksik çevirileri test etmek ve doldurmak için `intlayer` komutunu kullanabilirsiniz.

package/docs/tr/per_locale_file.md

@@ -126,7 +126,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-Bu yapılandırmayı kullanarak, tüm yerel ayar başına dosyalar varsayılan yerel ayar İngilizce olarak ayarlanmış şekilde oluşturulacaktır. Ayrıca `extract` komutu kullanılarak `.content` dosyalarının oluşturulmasını ve derleyiciyi (compiler) içerir. (Daha fazla bilgi için [Compiler](https://intlayer.org/doc/compiler) veya [Extract](https://intlayer.org/doc/concept/cli/extract) bölümlerine bakın.)
+Bu yapılandırmayı kullanarak, tüm yerel ayar başına dosyalar varsayılan yerel ayar İngilizce olarak ayarlanmış şekilde oluşturulacaktır. Ayrıca `extract` komutu kullanılarak `.content` dosyalarının oluşturulmasını ve derleyiciyi (compiler) içerir. (Daha fazla bilgi için [Compiler](https://intlayer.org/doc/compiler) veya [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md) bölümlerine bakın.)
 
 ## Yerel Ayar Başına Format
 

package/docs/uk/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** використовується для розповсюдження мови до клієнтських компонентів-нащадків.
 - Водночас **`IntlayerServerProvider`** використовується для забезпечення мови серверним компонентам-нащадкам.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Опціонально) Крок 7: Заповнення відсутніх перекладів
 
 Intlayer надає CLI-інструмент, щоб допомогти вам заповнити відсутні переклади. Ви можете використовувати команду `intlayer` для перевірки та заповнення відсутніх перекладів із вашого коду.

package/docs/vi/intlayer_with_nextjs_15.md

@@ -659,7 +659,7 @@ const Page = async ({ params }) => {
 
   > Layout và trang không thể chia sẻ một ngữ cảnh server chung vì hệ thống ngữ cảnh server dựa trên kho dữ liệu theo từng yêu cầu (thông qua cơ chế [React's cache](https://react.dev/reference/react/cache)), khiến mỗi "context" được tạo lại cho các phân đoạn khác nhau của ứng dụng. Việc đặt provider trong một layout dùng chung sẽ phá vỡ sự cô lập này, ngăn cản việc truyền đúng giá trị ngữ cảnh server đến các component server của bạn.
 
-> Layout và trang không thể chia sẻ một context server chung vì hệ thống context server dựa trên kho dữ liệu theo từng yêu cầu (qua cơ chế [React's cache](https://react.dev/reference/react/cache)), dẫn đến mỗi "context" được tạo lại cho các phân đoạn khác nhau của ứng dụng. Việc đặt provider trong một layout dùng chung sẽ phá vỡ sự cô lập này, ngăn cản việc truyền đúng các giá trị context server đến các component server của bạn.
+  > Layout và trang không thể chia sẻ một context server chung vì hệ thống context server dựa trên kho dữ liệu theo từng yêu cầu (qua cơ chế [React's cache](https://react.dev/reference/react/cache)), dẫn đến mỗi "context" được tạo lại cho các phân đoạn khác nhau của ứng dụng. Việc đặt provider trong một layout dùng chung sẽ phá vỡ sự cô lập này, ngăn cản việc truyền đúng các giá trị context server đến các component server của bạn.
 
 ```tsx {4,7} fileName="src/components/ClientComponentExample.tsx" codeFormat="typescript"
 "use client";

package/docs/vi/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** được sử dụng để cung cấp ngôn ngữ cho các thành phần con phía client.
 - Trong khi **`IntlayerServerProvider`** được sử dụng để cung cấp ngôn ngữ cho các thành phần con phía server.
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (Tùy chọn) Bước 7: Điền các bản dịch còn thiếu
 
 Intlayer cung cấp một công cụ CLI để giúp bạn điền các bản dịch còn thiếu. Bạn có thể sử dụng lệnh `intlayer` để kiểm tra và điền các bản dịch còn thiếu từ mã của mình.

package/docs/vi/intlayer_with_nextjs_no_locale_path.md

@@ -720,6 +720,7 @@ const Page: NextPage = async () => {
 
 > Layout và page không thể chia sẻ cùng một server context vì hệ thống server context dựa trên một kho dữ liệu theo từng yêu cầu (thông qua cơ chế [React's cache](https://react.dev/reference/react/cache)), khiến mỗi "context" được tạo lại cho các đoạn khác nhau của ứng dụng. Đặt provider trong một layout chia sẻ sẽ phá vỡ sự cô lập này, ngăn việc truyền đúng các giá trị server context tới các server component của bạn.
 
+
 ```tsx {4,7} fileName="src/components/clientComponentExample/ClientComponentExample.tsx" codeFormat="typescript"
 "use client";
 

package/docs/vi/per_locale_file.md

@@ -128,7 +128,7 @@ const config: IntlayerConfig = {
 export default config;
 ```
 
-Sử dụng cấu hình này, tất cả các tệp theo từng locale sẽ được tạo với locale mặc định được đặt là tiếng Anh. Nó cũng bao gồm việc tạo các tệp `.content` bằng cách sử dụng lệnh `extract` và compiler. (Xem [Compiler](https://intlayer.org/doc/compiler) hoặc [Extract](https://intlayer.org/doc/concept/cli/extract) để biết thêm thông tin.)
+Sử dụng cấu hình này, tất cả các tệp theo từng locale sẽ được tạo với locale mặc định được đặt là tiếng Anh. Nó cũng bao gồm việc tạo các tệp `.content` bằng cách sử dụng lệnh `extract` và compiler. (Xem [Compiler](https://intlayer.org/doc/compiler) hoặc [Extract](https://github.com/aymericzip/intlayer/edit/main/docs/docs/en/cli/extract.md) để biết thêm thông tin.)
 
 ## Định dạng theo từng locale
 

package/docs/zh/intlayer_with_nextjs_compiler.md

@@ -338,6 +338,8 @@ export default async function Page() {
 - **`IntlayerClientProvider`** 用于在客户端向子组件提供语言环境。
 - 而 **`IntlayerServerProvider`** 用于在服务器端向子组件提供语言环境。
 
+  > Layout and page cannot share a common server context because the server context system is based on a per-request data store (via [React's cache](https://react.dev/reference/react/cache) mechanism), causing each "context" to be re-created for different segments of the application. Placing the provider in a shared layout would break this isolation, preventing the correct propagation of the server context values to your server components.
+
 ### (可选) 第 7 步：填写缺失的翻译
 
 Intlayer 提供了一个 CLI 工具来帮助您填写缺失的翻译。您可以使用 `intlayer` 命令来测试并从您的代码中填写缺失的翻译。

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@intlayer/docs",
-  "version": "8.2.2",
+  "version": "8.2.4",
   "private": false,
   "description": "Intlayer documentation",
   "keywords": [
@@ -72,20 +72,20 @@
     "watch": "webpack --config ./webpack.config.ts --watch"
   },
   "dependencies": {
-    "@intlayer/config": "8.2.2",
-    "@intlayer/core": "8.2.2",
-    "@intlayer/types": "8.2.2"
+    "@intlayer/config": "8.2.3",
+    "@intlayer/core": "8.2.3",
+    "@intlayer/types": "8.2.3"
   },
   "devDependencies": {
-    "@intlayer/api": "8.2.2",
-    "@intlayer/cli": "8.2.2",
-    "@types/node": "25.3.3",
+    "@intlayer/api": "8.2.3",
+    "@intlayer/cli": "8.2.3",
+    "@types/node": "25.3.5",
     "@utils/ts-config": "1.0.4",
     "@utils/ts-config-types": "1.0.4",
     "@utils/tsdown-config": "1.0.4",
     "fast-glob": "3.3.3",
     "rimraf": "6.1.3",
-    "tsdown": "0.20.3",
+    "tsdown": "0.21.0",
     "typescript": "5.9.3",
     "vitest": "4.0.18"
   },