-
@tolgee/i18next withTolgee not working with React Native.
config:
```
import i18n, {ThirdPartyModule} from 'i18next';
import {initReactI18next} from 'react-i18next';
import AsyncStorage from '…
-
## Rationale
1. This was previously attempted by the automated dependabot job but the PR tests failed.
1. This issue has been created to fix the issue as there may be multiple dependency requirement…
-
**What version of this package are you using?**
when i used next-translate-plugin with @module-federation/nextjs-mf, useTranslation not working! help
**What operating system, Node.js, and npm versio…
-
i18next-react project setup:
```js
// ./i18n-unused.config.cjs
module.exports = {
localesPath: 'src/analysis/_locales',
srcPath: 'src',
};
```
translation files
```
./src/analysis/_l…
-
## 🚀 Feature Proposal
True namespace detection through static function call analysis, or through allowing easy project-specific config.
See example below for what I would like to achieve.
…
-
**Describe the bug**
I use this vscode plugin in my React project.
I have multiple translation files under folders like `en/common.json`, `zh/common.json`, to split one big json file into maintain…
-
# 1. Translation keys
We need to replace all string constants with translation keys.
For example,
```
```
should become
```
import { CONNECTIONS } from "i18n/namespaces";
...
const { t…
-
**Describe the bug**
When I have multiple translation function in the same component, such as `const t = useTranslations('namespace')` and `const tCommon = useTranslations('common')`, they are not pa…
-
## 🐛 Bug Report
When using the `useTranslation` hook to get two different TFunctions scoped to different namespaces, extraction should place keys into the namespace of the corresponding TFuncti…
-
**What version of this package are you using?**
2.0.3 & 2.0.4
NextJS 13, app directory
**What operating system, Node.js, and npm version?**
MacOS/Github actions (debian), node v19.6.0
**What …