Adriano Raiano

btw: _ is used as context separator or as plural suffix... so maybe also change that if you don't use these features... https://www.i18next.com/overview/typescript#custom-type-options `contextSeparator: '__something_else__'` `pluralSeparator: '__something_else__'`

@adil-hublo please provide a minimal reproducible example repository we can use to investigate

> Could the types be resolved differently when loading the translations from a `.json` file? You mean like [this](https://github.com/i18next/i18next/blob/master/examples/typescript/i18n/config.ts#L2)? => https://www.i18next.com/overview/typescript#not-working-interpolation-values

> Oh, sorry. In my case, the translations are loaded using [the HTTP backend](https://github.com/i18next/i18next-http-backend). > > We then have a `.d.ts` file that adds to the types that looks generally...

Have also a look at: https://github.com/locize/i18next-typescript-examples

> [#2240 (comment)](https://github.com/i18next/i18next/issues/2240#issuecomment-2361597411) > > in your example I see you are using `23.15.0` though, which is a totally fine version for me. > > Here is a minimal reproduction...

stale... so closing for now...

1. Create a new test file and pass in a logger dummy like here: https://github.com/i18next/i18next/blob/master/test/runtime/i18next.hasLoadedNamespace.test.js#L4 2. if check is ok... no optional chaining 3. why should dev be ignored... `fallbackLng`...

> Some tests pass "dev" as a fallback even though it's not in supported languages so I wasn't sure if there was some behavior I'm not aware of, okay will...

totally forgot that... yes... it's already there ;-) Yes, it should be called also via react-i18next...