@intlayer/docs 7.0.8 → 7.0.9-canary.0

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
+```

package/frequent_questions/es/package_version_error.md

@@ -0,0 +1,132 @@
+---
+createdAt: 2025-05-20
+updatedAt: 2025-06-29
+title: Obtengo un error relacionado con los sub-paquetes `@intlayer/*`
+description: Soluciona el error relacionado con los sub-paquetes `@intlayer/*`.
+keywords:
+  - @intlayer/*
+  - sub-paquetes
+  - intlayer
+slugs:
+  - frequent-questions
+  - package-version-error
+---
+
+# Obtengo un error relacionado con los sub-paquetes `@intlayer/*`
+
+Este problema suele ocurrir después de una actualización de los paquetes de Intlayer.
+
+Ejemplo de mensaje de error:
+
+```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";
+  |                            ~~~~~~~~~~~~~~~~~~~~
+```
+
+## Razón
+
+Los paquetes base como `intlayer`, `react-intlayer`, `react-native-intlayer`, `vue-intlayer` están reutilizando los mismos sub-paquetes como `@intlayer/config`, `@intlayer/core`, `@intlayer/types` para evitar la duplicación de código.
+
+Entre dos versiones, no se garantiza que las exportaciones de los sub-paquetes sean las mismas. Para limitar este problema, intlayer fija la versión de los sub-paquetes a la versión del paquete principal.
+
+> Ej: `intlayer@1.0.0` usa `@intlayer/config@1.0.0`, `@intlayer/core@1.0.0`, `@intlayer/types@1.0.0`
+
+> (Excepto para `@intlayer/swc`), los sub-paquetes `@intlayer/*` no están destinados a ser usados directamente. Por lo tanto, recomendamos no instalarlos directamente.
+
+## Resolución
+
+1. Asegúrate de que las versiones del paquete principal y de los sub-paquetes sean las mismas.
+
+```json5
+{
+  "dependencies": {
+    "intlayer": "7.0.1",
+    "react-intlayer": "7.0.0", // Versión incorrecta, debería ser 7.0.1
+  },
+  "devDependencies": {
+    "intlayer-editor": "7.0.1",
+  },
+}
+```
+
+2. Intenta eliminar el lockfile y la carpeta node_modules y reinstalar las dependencias.
+
+A veces, el gestor de paquetes mantiene una versión antigua de los sub-paquetes en el lockfile o en la caché. Para solucionar esto, puedes intentar eliminar el lockfile y la carpeta node_modules y reinstalar las dependencias.
+
+```bash
+rm -rf package-lock.json node_modules
+npm install
+```
+
+3. Verifica la instalación global
+
+Recomendamos instalar `intlayer` o `intlayer-cli` globalmente para acceder a los comandos CLI. Si la versión global no es la misma que la versión local, el gestor de paquetes puede considerar la versión incorrecta.
+
+**Verificar si un paquete está instalado globalmente**
+
+```bash
+npm list -g --depth=0
+```
+
+```bash
+npm list -g --depth=0 | grep intlayer
+```
+
+```bash
+yarn global list
+```
+
+```bash
+pnpm list -g --depth=0
+```
+
+**Soluciona posibles conflictos de dependencias globales**
+
+```bash
+npm uninstall -g intlayer intlayer-cli
+```
+
+```bash
+yarn global remove intlayer intlayer-cli
+```
+
+```bash
+pnpm remove -g intlayer intlayer-cli
+```
+
+5. Intenta limpiar la caché
+
+En algunos entornos como docker, github actions o plataformas de hosting web como Vercel, puede existir una caché. Puedes intentar limpiar la caché y volver a intentar la instalación.
+
+También puedes intentar limpiar la caché de tu gestor de paquetes con el siguiente comando:
+
+```bash
+npm cache clean --force
+```
+
+```bash
+yarn cache clean
+```
+
+```bash
+pnpm cache clean
+```

package/frequent_questions/fr/package_version_error.md

@@ -0,0 +1,132 @@
+---
+createdAt: 2025-05-20
+updatedAt: 2025-06-29
+title: Je rencontre une erreur liée aux sous-paquets `@intlayer/*`
+description: Résoudre une erreur liée aux sous-paquets `@intlayer/*`.
+keywords:
+  - @intlayer/*
+  - sous-paquets
+  - intlayer
+slugs:
+  - frequent-questions
+  - package-version-error
+---
+
+# Je rencontre une erreur liée aux sous-paquets `@intlayer/*`
+
+Ce problème survient généralement après une mise à jour des paquets Intlayer.
+
+Exemple de message d'erreur :
+
+```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";
+  |          ~~~~~~~~~~~~~~~~
+
+✖ ERREUR  Aucune exportation correspondante dans "node_modules/@intlayer/config/dist/esm/client.mjs" pour l'import "configESMxCJSRequire"
+
+node_modules/@intlayer/unmerged-dictionaries-entry/dist/esm/index.mjs:3:27:
+3 | import { clearModuleCache, configESMxCJSRequire } from "@intlayer/config";
+  |                            ~~~~~~~~~~~~~~~~~~~~
+```
+
+## Raison
+
+Les paquets de base tels que `intlayer`, `react-intlayer`, `react-native-intlayer`, `vue-intlayer` réutilisent les mêmes sous-paquets que `@intlayer/config`, `@intlayer/core`, `@intlayer/types` afin d'éviter la duplication de code.
+
+Entre deux versions, les exports des sous-paquets ne sont pas garantis d’être les mêmes. Pour limiter ce problème, intlayer fixe la version des sous-paquets à la version du paquet principal.
+
+> Ex : `intlayer@1.0.0` utilise `@intlayer/config@1.0.0`, `@intlayer/core@1.0.0`, `@intlayer/types@1.0.0`
+
+> (À l’exception de `@intlayer/swc`), les sous-paquets `@intlayer/*` ne sont pas destinés à être utilisés directement. Nous recommandons donc de ne pas les installer directement.
+
+## Résolution
+
+1. Assurez-vous que les versions du paquet principal et des sous-paquets sont identiques.
+
+```json5
+{
+  "dependencies": {
+    "intlayer": "7.0.1",
+    "react-intlayer": "7.0.0", // Mauvaise version, cela devrait être 7.0.1
+  },
+  "devDependencies": {
+    "intlayer-editor": "7.0.1",
+  },
+}
+```
+
+2. Essayez de supprimer le fichier de verrouillage (lockfile) et le dossier node_modules, puis réinstallez les dépendances.
+
+Parfois, le gestionnaire de paquets conserve une ancienne version des sous-paquets dans le fichier de verrouillage en cache. Pour résoudre ce problème, vous pouvez essayer de supprimer le fichier de verrouillage et le dossier node_modules, puis réinstaller les dépendances.
+
+```bash
+rm -rf package-lock.json node_modules
+npm install
+```
+
+3. Vérifiez l'installation globale
+
+Nous recommandons d’installer `intlayer` ou `intlayer-cli` globalement pour accéder aux commandes CLI. Si la version globale n’est pas la même que la version locale, le gestionnaire de paquets peut considérer la mauvaise version.
+
+**Vérifier si un paquet est installé globalement**
+
+```bash
+npm list -g --depth=0
+```
+
+```bash
+npm list -g --depth=0 | grep intlayer
+```
+
+```bash
+yarn global list
+```
+
+```bash
+pnpm list -g --depth=0
+```
+
+**Résoudre les conflits potentiels de dépendances globales**
+
+```bash
+npm uninstall -g intlayer intlayer-cli
+```
+
+```bash
+yarn global remove intlayer intlayer-cli
+```
+
+```bash
+pnpm remove -g intlayer intlayer-cli
+```
+
+5. Essayez de nettoyer le cache
+
+Pour certains environnements comme docker, github actions, ou les plateformes d’hébergement web comme Vercel, un cache peut être présent. Vous pouvez essayer de nettoyer le cache et de réessayer l’installation.
+
+Vous pouvez également essayer de nettoyer le cache de votre gestionnaire de paquets avec la commande suivante :
+
+```bash
+npm cache clean --force
+```
+
+```bash
+yarn cache clean
+```
+
+```bash
+pnpm cache clean
+```

package/frequent_questions/hi/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";
+  |          ~~~~~~~~~~~~~~~~
+
+✖ 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";
+  |                            ~~~~~~~~~~~~~~~~~~~~
+```
+
+## कारण
+
+बेस पैकेज जैसे `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. वैश्विक इंस्टॉलेशन की जांच करें
+
+CLI कमांड्स तक पहुँचने के लिए हम सुझाव देते हैं कि `intlayer` या `intlayer-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
+```