@intlayer/docs 7.0.8 → 7.0.9-canary.2

package/docs/vi/readme.md

@@ -22,11 +22,11 @@
   </a>
     <a href="https://github.com/aymericzip/intlayer/stargazers" target="_blank"><img src="https://img.shields.io/github/stars/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logo=github&logoColor=FFD700" alt="Số sao trên GitHub" height="24"/>
   </a>
-  <a href="https://www.npmjs.org/package/intlayer" target="_blank"><img src="https://img.shields.io/npm/dm/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000" alt="lượt tải hàng tháng" height="24"/>
+  <a href="https://www.npmjs.org/package/intlayer" target="_blank"><img src="https://img.shields.io/npm/dm/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000&cacheSeconds=86400" alt="lượt tải hàng tháng" height="24"/>
   </a>
-  <a href="https://github.com/aymericzip/intlayer/blob/main/LICENSE"><img src="https://img.shields.io/github/license/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000" alt="giấy phép"/>
+  <a href="https://github.com/aymericzip/intlayer/blob/main/LICENSE"><img src="https://img.shields.io/github/license/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000&cacheSeconds=86400" alt="giấy phép"/>
   </a>
-  <a href="https://github.com/aymericzip/intlayer/commits/main"><img src="https://img.shields.io/github/last-commit/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000" alt="lần cam kết cuối cùng"/>
+  <a href="https://github.com/aymericzip/intlayer/commits/main"><img src="https://img.shields.io/github/last-commit/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000&cacheSeconds=86400" alt="lần cam kết cuối cùng"/>
   </a>
 </p>
 

package/docs/zh/readme.md

@@ -22,11 +22,11 @@
   </a>
     <a href="https://github.com/aymericzip/intlayer/stargazers" target="_blank"><img src="https://img.shields.io/github/stars/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logo=github&logoColor=FFD700" alt="GitHub 星标" height="24"/>
   </a>
-  <a href="https://www.npmjs.org/package/intlayer" target="_blank"><img src="https://img.shields.io/npm/dm/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000" alt="月下载量" height="24"/>
+  <a href="https://www.npmjs.org/package/intlayer" target="_blank"><img src="https://img.shields.io/npm/dm/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000&cacheSeconds=86400" alt="月下载量" height="24"/>
   </a>
-  <a href="https://github.com/aymericzip/intlayer/blob/main/LICENSE"><img src="https://img.shields.io/github/license/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000" alt="许可证"/>
+  <a href="https://github.com/aymericzip/intlayer/blob/main/LICENSE"><img src="https://img.shields.io/github/license/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000&cacheSeconds=86400" alt="许可证"/>
   </a>
-  <a href="https://github.com/aymericzip/intlayer/commits/main"><img src="https://img.shields.io/github/last-commit/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000" alt="最新提交"/>
+  <a href="https://github.com/aymericzip/intlayer/commits/main"><img src="https://img.shields.io/github/last-commit/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000&cacheSeconds=86400" alt="最新提交"/>
   </a>
 </p>
 

package/frequent_questions/ar/package_version_error.md

@@ -0,0 +1,132 @@
+---
+createdAt: 2025-05-20
+updatedAt: 2025-06-29
+title: أحصل على خطأ متعلق بالحزم الفرعية @intlayer/*
+description: إصلاح الخطأ المتعلق بالحزم الفرعية @intlayer/*.
+keywords:
+  - @intlayer/*
+  - الحزم الفرعية
+  - intlayer
+slugs:
+  - frequent-questions
+  - package-version-error
+---
+
+# أحصل على خطأ متعلق بالحزم الفرعية `@intlayer/*`
+
+عادةً ما تحدث هذه المشكلة بعد تحديث حزم Intlayer.
+
+مثال على رسالة الخطأ:
+
+```bash
+Error: Cannot find module '@intlayer/types'
+```
+
+```bash
+TypeError: (0 , __intlayer_config_client.colorize) is not a function
+
+at import { colorize } from '@intlayer/config';
+```
+
+```bash
+✖ ERROR  No matching export in "node_modules/@intlayer/config/dist/esm/client.mjs" for import "clearModuleCache"
+
+node_modules/@intlayer/unmerged-dictionaries-entry/dist/esm/index.mjs:3:9:
+3 | import { clearModuleCache, configESMxCJSRequire } from "@intlayer/config";
+  |          ~~~~~~~~~~~~~~~~
+
+✖ خطأ  لا يوجد تصدير مطابق في "node_modules/@intlayer/config/dist/esm/client.mjs" للاستيراد "configESMxCJSRequire"
+
+node_modules/@intlayer/unmerged-dictionaries-entry/dist/esm/index.mjs:3:27:
+3 | import { clearModuleCache, configESMxCJSRequire } from "@intlayer/config";
+  |                            ~~~~~~~~~~~~~~~~~~~~
+```
+
+## السبب
+
+الحزم الأساسية مثل `intlayer`، `react-intlayer`، `react-native-intlayer`، `vue-intlayer` تعيد استخدام نفس الحزم الفرعية مثل `@intlayer/config`، `@intlayer/core`، `@intlayer/types` لتجنب تكرار الكود.
+
+بين إصدارين، لا يتم ضمان أن تكون التصديرات في الحزم الفرعية هي نفسها. للحد من هذه المشكلة، يقوم intlayer بتثبيت إصدار الحزم الفرعية ليتطابق مع إصدار الحزمة الرئيسية.
+
+> مثال: `intlayer@1.0.0` يستخدم `@intlayer/config@1.0.0`، `@intlayer/core@1.0.0`، `@intlayer/types@1.0.0`
+
+> (باستثناء `@intlayer/swc`)، الحزم الفرعية `@intlayer/*` ليست مخصصة للاستخدام المباشر. لذلك نوصي بعدم تثبيتها مباشرة.
+
+## الحل
+
+1. تأكد من أن إصدارات الحزمة الرئيسية والحزم الفرعية هي نفسها.
+
+```json5
+{
+  "dependencies": {
+    "intlayer": "7.0.1",
+    "react-intlayer": "7.0.0", // إصدار خاطئ، يجب أن يكون 7.0.1
+  },
+  "devDependencies": {
+    "intlayer-editor": "7.0.1",
+  },
+}
+```
+
+2. حاول إزالة ملف القفل ومجلد node_modules وأعد تثبيت التبعيات.
+
+أحيانًا، يحتفظ مدير الحزم بإصدار قديم من الحزم الفرعية في ملف القفل ضمن الكاش. لإصلاح ذلك، يمكنك محاولة إزالة ملف القفل ومجلد node_modules وأعد تثبيت التبعيات.
+
+```bash
+rm -rf package-lock.json node_modules
+npm install
+```
+
+3. تحقق من التثبيت العالمي
+
+نوصي بتثبيت `intlayer` أو `intlayer-cli` بشكل عالمي للوصول إلى أوامر CLI. إذا لم يكن الإصدار العالمي هو نفسه الإصدار المحلي، قد يعتبر مدير الحزم الإصدار خاطئًا.
+
+**تحقق مما إذا كانت الحزمة مثبتة عالميًا**
+
+```bash
+npm list -g --depth=0
+```
+
+```bash
+npm list -g --depth=0 | grep intlayer
+```
+
+```bash
+yarn global list
+```
+
+```bash
+pnpm list -g --depth=0
+```
+
+**إصلاح تعارضات التبعيات العالمية المحتملة**
+
+```bash
+npm uninstall -g intlayer intlayer-cli
+```
+
+```bash
+yarn global remove intlayer intlayer-cli
+```
+
+```bash
+pnpm remove -g intlayer intlayer-cli
+```
+
+5. حاول تنظيف الكاش
+
+في بعض البيئات مثل docker، أو github actions، أو منصات استضافة الويب مثل Vercel، قد يكون هناك كاش موجود. يمكنك محاولة تنظيف الكاش وإعادة محاولة التثبيت.
+
+يمكنك أيضًا محاولة تنظيف كاش مدير الحزم الخاص بك باستخدام الأمر التالي:
+
+```bash
+npm cache clean --force
+```
+
+```bash
+yarn cache clean
+```
+
+```bash
+pnpm cache clean
+```

package/frequent_questions/de/package_version_error.md

@@ -0,0 +1,132 @@
+---
+createdAt: 2025-05-20
+updatedAt: 2025-06-29
+title: Ich erhalte einen Fehler im Zusammenhang mit Sub-Paketen `@intlayer/*`
+description: Fehlerbehebung im Zusammenhang mit Sub-Paketen `@intlayer/*`.
+keywords:
+  - @intlayer/*
+  - Sub-Pakete
+  - intlayer
+slugs:
+  - frequent-questions
+  - package-version-error
+---
+
+# Ich erhalte einen Fehler im Zusammenhang mit Sub-Paketen `@intlayer/*`
+
+Dieses Problem tritt normalerweise nach einem Update der Intlayer-Pakete auf.
+
+Beispiel für eine Fehlermeldung:
+
+```bash
+Error: Cannot find module '@intlayer/types'
+```
+
+```bash
+TypeError: (0 , __intlayer_config_client.colorize) is not a function
+
+at import { colorize } from '@intlayer/config';
+```
+
+```bash
+✖ ERROR  Kein passender Export in "node_modules/@intlayer/config/dist/esm/client.mjs" für den Import "clearModuleCache"
+
+node_modules/@intlayer/unmerged-dictionaries-entry/dist/esm/index.mjs:3:9:
+3 | import { clearModuleCache, configESMxCJSRequire } from "@intlayer/config";
+  |          ~~~~~~~~~~~~~~~~
+
+✖ FEHLER Kein passender Export in "node_modules/@intlayer/config/dist/esm/client.mjs" für den Import "configESMxCJSRequire"
+
+node_modules/@intlayer/unmerged-dictionaries-entry/dist/esm/index.mjs:3:27:
+3 | import { clearModuleCache, configESMxCJSRequire } from "@intlayer/config";
+  |                            ~~~~~~~~~~~~~~~~~~~~
+```
+
+## Grund
+
+Basispakete wie `intlayer`, `react-intlayer`, `react-native-intlayer`, `vue-intlayer` verwenden dieselben Sub-Pakete wie `@intlayer/config`, `@intlayer/core`, `@intlayer/types` erneut, um Code-Duplikationen zu vermeiden.
+
+Zwischen zwei Versionen ist nicht garantiert, dass die Exporte der Sub-Pakete gleich sind. Um dieses Problem zu begrenzen, fixiert intlayer die Version der Sub-Pakete auf die Version des Hauptpakets.
+
+> Beispiel: `intlayer@1.0.0` verwendet `@intlayer/config@1.0.0`, `@intlayer/core@1.0.0`, `@intlayer/types@1.0.0`
+
+> (Außer `@intlayer/swc`) sind `@intlayer/*` Sub-Pakete nicht für die direkte Verwendung gedacht. Daher empfehlen wir, diese nicht direkt zu installieren.
+
+## Lösung
+
+1. Stellen Sie sicher, dass die Versionen des Hauptpakets und der Sub-Pakete identisch sind.
+
+```json5
+{
+  "dependencies": {
+    "intlayer": "7.0.1",
+    "react-intlayer": "7.0.0", // Falsche Version, es sollte 7.0.1 sein
+  },
+  "devDependencies": {
+    "intlayer-editor": "7.0.1",
+  },
+}
+```
+
+2. Versuchen Sie, die Lockdatei und den node_modules-Ordner zu entfernen und die Abhängigkeiten neu zu installieren.
+
+Manchmal behält der Paketmanager eine alte Version der Sub-Pakete im Cache der Lockdatei. Um dies zu beheben, können Sie versuchen, die Lockdatei und den node_modules-Ordner zu entfernen und die Abhängigkeiten neu zu installieren.
+
+```bash
+rm -rf package-lock.json node_modules
+npm install
+```
+
+3. Überprüfen Sie die globale Installation
+
+Wir empfehlen, `intlayer` oder `intlayer-cli` global zu installieren, um auf die CLI-Befehle zugreifen zu können. Wenn die globale Version nicht mit der lokalen Version übereinstimmt, kann der Paketmanager die falsche Version verwenden.
+
+**Überprüfen, ob ein Paket global installiert ist**
+
+```bash
+npm list -g --depth=0
+```
+
+```bash
+npm list -g --depth=0 | grep intlayer
+```
+
+```bash
+yarn global list
+```
+
+```bash
+pnpm list -g --depth=0
+```
+
+**Beheben Sie mögliche globale Abhängigkeitskonflikte**
+
+```bash
+npm uninstall -g intlayer intlayer-cli
+```
+
+```bash
+yarn global remove intlayer intlayer-cli
+```
+
+```bash
+pnpm remove -g intlayer intlayer-cli
+```
+
+5. Versuchen Sie, den Cache zu bereinigen
+
+In einigen Umgebungen wie Docker, GitHub Actions oder Webhosting-Plattformen wie Vercel kann ein Cache vorhanden sein. Sie können versuchen, den Cache zu bereinigen und die Installation erneut durchzuführen.
+
+Sie können auch versuchen, den Cache Ihres Paketmanagers mit folgendem Befehl zu bereinigen:
+
+```bash
+npm cache clean --force
+```
+
+```bash
+yarn cache clean
+```
+
+```bash
+pnpm cache clean
+```

package/frequent_questions/en/package_version_error.md

@@ -0,0 +1,153 @@
+---
+createdAt: 2025-05-20
+updatedAt: 2025-06-29
+title: I get an error related to sub-packages @intlayer/*
+description: Fix error related to sub-packages @intlayer/*.
+keywords:
+  - @intlayer/*
+  - sub-packages
+  - intlayer
+slugs:
+  - frequent-questions
+  - package-version-error
+---
+
+# I get an error related to sub-packages `@intlayer/*`
+
+This problem usually occurs after an update of the Intlayer packages.
+
+Example of error message:
+
+```bash
+Error: Cannot find module '@intlayer/types'
+```
+
+```bash
+TypeError: (0 , __intlayer_config_client.colorize) is not a function
+
+at import { colorize } from '@intlayer/config';
+```
+
+```bash
+✖ ERROR  No matching export in "node_modules/@intlayer/config/dist/esm/client.mjs" for import "clearModuleCache"
+
+node_modules/@intlayer/unmerged-dictionaries-entry/dist/esm/index.mjs:3:9:
+3 | import { clearModuleCache, configESMxCJSRequire } from "@intlayer/config";
+  |          ~~~~~~~~~~~~~~~~
+
+✖ ERROR  No matching export in "node_modules/@intlayer/config/dist/esm/client.mjs" for import "configESMxCJSRequire"
+
+node_modules/@intlayer/unmerged-dictionaries-entry/dist/esm/index.mjs:3:27:
+3 | import { clearModuleCache, configESMxCJSRequire } from "@intlayer/config";
+  |                            ~~~~~~~~~~~~~~~~~~~~
+```
+
+## Reason
+
+Base packages as `intlayer`, `react-intlayer`, `react-native-intlayer`, `vue-intlayer` are reusing the same sub-packages as `@intlayer/config`, `@intlayer/core`, `@intlayer/types` to avoid code duplication.
+
+Between two versions, the exports of the sub-packages are not guaranteed to be the same. To limit this problem, intlayer pins the version of the sub-packages to the version of the main package.
+
+> Ex: `intlayer@1.0.0` uses `@intlayer/config@1.0.0`, `@intlayer/core@1.0.0`, `@intlayer/types@1.0.0`
+
+> (Except for `@intlayer/swc`), `@intlayer/*` sub-packages are not meant to be used directly. So we recommend to do not install them directly.
+
+## Resolution
+
+1. Ensure the versions of the main package and the sub-packages are the same.
+
+```json5
+{
+  "dependencies": {
+    "intlayer": "7.0.1",
+    "react-intlayer": "7.0.0", // Wrong version, it should be 7.0.1
+  },
+  "devDependencies": {
+    "intlayer-editor": "7.0.1",
+  },
+}
+```
+
+2. Try to remove the lockfile and node_modules folder and reinstall the dependencies.
+
+Sometimes, the package manager keep an old version of the sub-packages in the lockfile in cache. To fix this, you can try to remove the lockfile and node_modules folder and reinstall the dependencies.
+
+```bash
+rm -rf package-lock.json node_modules
+
+npm install # or yarn install or pnpm install or bun pm install
+```
+
+3. Check global installation
+
+We recommend to install `intlayer` or `intlayer-cli` globally to access the CLI commands. If the global version is not the same as the local version, the package manager may consider the wrong version.
+
+**Check if a package is installed globally**
+
+```bash
+npm list -g --depth=3 | grep intlayer
+```
+
+```bash
+yarn global list --depth=3 | grep intlayer
+```
+
+```bash
+pnpm list -g --depth=3 | grep intlayer
+```
+
+```bash
+bun pm ls -g --depth=3 | grep intlayer
+```
+
+**Fix potential global dependency conflicts**
+
+```bash
+npm uninstall -g intlayer intlayer-cli
+```
+
+```bash
+yarn global remove intlayer intlayer-cli
+```
+
+```bash
+pnpm remove -g intlayer intlayer-cli
+```
+
+```bash
+bun pm rm -g intlayer intlayer-cli
+```
+
+5. Try cleaning the cache
+
+For some environments as docker, github actions, or web hosting platforms as Vercel, a cache can be present. You can try to clean the cache and retry the installation.
+
+You can also try to clean the cache of your package manager with the following command:
+
+```bash
+npm cache clean --force
+```
+
+```bash
+yarn cache clean
+```
+
+```bash
+pnpm cache clean
+```
+
+```bash
+bun pm cache clean
+```
+
+6. Try removing the `.intlayer` folder
+
+Intlayer cache a bundled version of his version itself in the `.intlayer/cache` folder.
+
+This cache can be corrupted if the version of intlayer is not the same as the version of the cached version.
+
+You can try to remove the `.intlayer` folder and retry the build.
+
+```bash
+rm -rf .intlayer
+```

package/frequent_questions/en-GB/package_version_error.md

@@ -0,0 +1,132 @@
+---
+createdAt: 2025-05-20
+updatedAt: 2025-06-29
+title: I get an error related to sub-packages @intlayer/*
+description: Fix error related to sub-packages @intlayer/*.
+keywords:
+  - @intlayer/*
+  - sub-packages
+  - intlayer
+slugs:
+  - frequent-questions
+  - package-version-error
+---
+
+# I get an error related to sub-packages `@intlayer/*`
+
+This issue usually arises after updating the Intlayer packages.
+
+Example of error message:
+
+```bash
+Error: Cannot find module '@intlayer/types'
+```
+
+```bash
+TypeError: (0 , __intlayer_config_client.colorize) is not a function
+
+at import { colorize } from '@intlayer/config';
+```
+
+```bash
+✖ ERROR  No matching export in "node_modules/@intlayer/config/dist/esm/client.mjs" for import "clearModuleCache"
+
+node_modules/@intlayer/unmerged-dictionaries-entry/dist/esm/index.mjs:3:9:
+3 | import { clearModuleCache, configESMxCJSRequire } from "@intlayer/config";
+  |          ~~~~~~~~~~~~~~~~
+
+✖ ERROR  No matching export in "node_modules/@intlayer/config/dist/esm/client.mjs" for import "configESMxCJSRequire"
+
+node_modules/@intlayer/unmerged-dictionaries-entry/dist/esm/index.mjs:3:27:
+3 | import { clearModuleCache, configESMxCJSRequire } from "@intlayer/config";
+  |                            ~~~~~~~~~~~~~~~~~~~~
+```
+
+## Reason
+
+Base packages such as `intlayer`, `react-intlayer`, `react-native-intlayer`, `vue-intlayer` reuse the same sub-packages like `@intlayer/config`, `@intlayer/core`, `@intlayer/types` to avoid code duplication.
+
+Between two versions, the exports of the sub-packages are not guaranteed to be the same. To limit this problem, intlayer pins the version of the sub-packages to the version of the main package.
+
+> Ex: `intlayer@1.0.0` uses `@intlayer/config@1.0.0`, `@intlayer/core@1.0.0`, `@intlayer/types@1.0.0`
+
+> (Except for `@intlayer/swc`), `@intlayer/*` sub-packages are not meant to be used directly. Therefore, we recommend not installing them directly.
+
+## Resolution
+
+1. Ensure the versions of the main package and the sub-packages are the same.
+
+```json5
+{
+  "dependencies": {
+    "intlayer": "7.0.1",
+    "react-intlayer": "7.0.0", // Incorrect version, it should be 7.0.1
+  },
+  "devDependencies": {
+    "intlayer-editor": "7.0.1",
+  },
+}
+```
+
+2. Try removing the lockfile and node_modules folder, then reinstall the dependencies.
+
+Sometimes, the package manager retains an old version of the sub-packages in the lockfile cache. To resolve this, you can try removing the lockfile and node_modules folder, then reinstall the dependencies.
+
+```bash
+rm -rf package-lock.json node_modules
+npm install
+```
+
+3. Check global installation
+
+We recommend installing `intlayer` or `intlayer-cli` globally to access the CLI commands. If the global version differs from the local version, the package manager may use the incorrect version.
+
+**Check if a package is installed globally**
+
+```bash
+npm list -g --depth=0
+```
+
+```bash
+npm list -g --depth=0 | grep intlayer
+```
+
+```bash
+yarn global list
+```
+
+```bash
+pnpm list -g --depth=0
+```
+
+**Fix potential global dependency conflicts**
+
+```bash
+npm uninstall -g intlayer intlayer-cli
+```
+
+```bash
+yarn global remove intlayer intlayer-cli
+```
+
+```bash
+pnpm remove -g intlayer intlayer-cli
+```
+
+5. Try cleaning the cache
+
+In some environments such as Docker, GitHub Actions, or web hosting platforms like Vercel, a cache may be present. You can try clearing the cache and retry the installation.
+
+You can also try clearing the cache of your package manager with the following command:
+
+```bash
+npm cache clean --force
+```
+
+```bash
+yarn cache clean
+```
+
+```bash
+pnpm cache clean
+```