You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When i18n is configured to use the resourcesToBackend feature such as with the provided config and the namespace files are not the same between languages, translations fail to be retrieved for the default language when referencing the file(s) with which there is a delta.
This results in the page becoming unresponsive and needing to be forcibly closed.
include a mis-matched set of JSON files across localizations:
locales
├── en
│ ├── addresses.json
│ ├── common.json
│ └── navigation.json
└── es
├── common.json
└── navigation.json
when rendering a component that uses the addresses namespace in this instance, the useTranslation hook will not be able to identify the namespace file.
This results in an infinite loop in the useTranslation hook (somewhere), resulting in the webpage "freezing", becoming unresponsive until the browser tab is closed.
Expected behavior
The configured i18n instance is able to load all files independent of what is available for other languages, and supply the text value for the one of the following:
the configured default language
the browser's set language
no translation, just use the placeholder text as if it couldn't be found normally
Your Environment
runtime version: node v22, any browser
i18next version: 24.2.1
i18next-resources-to-backend version: 1.2.1
os: Mac, linux kubernetes
The text was updated successfully, but these errors were encountered:
🐛 Bug Report
When i18n is configured to use the
resourcesToBackend
feature such as with the provided config and the namespace files are not the same between languages, translations fail to be retrieved for the default language when referencing the file(s) with which there is a delta.This results in the page becoming unresponsive and needing to be forcibly closed.
To Reproduce
Use this i18n configuration:
include a mis-matched set of JSON files across localizations:
when rendering a component that uses the
addresses
namespace in this instance, the useTranslation hook will not be able to identify the namespace file.This results in an infinite loop in the useTranslation hook (somewhere), resulting in the webpage "freezing", becoming unresponsive until the browser tab is closed.
Expected behavior
The configured i18n instance is able to load all files independent of what is available for other languages, and supply the text value for the one of the following:
Your Environment
The text was updated successfully, but these errors were encountered: