Aral Roca Gomez

Probably the problem is in the version of TypeScript inside the [next-translate-plugin](https://github.com/aralroca/next-translate-plugin). In order to updated we need to update also the TypeScript parser because has some breaking changes

Are your locales in `/locales/es/common.json` & `/locales/en/common.json`?

Not sure about the issue, can you try to remove the fallback blocking to verify if is for that? Otherwise, please provide a repo with the code to be easy...

Instead of `{t("common:example.title", { returnObjects: true })}` you can directly specify only the `example` to get the full array: `{t("common:example", { returnObjects: true })}`

Sorry, but I don't understand your problem. What is wrong in this code? ```js import { useTranslation } from 'next-translate' function Menu() { const { t } = useTranslation('common') const...

@joshuadesigner05 This problem is not related with the array, is related that you are trying to get translations in different languages at the same time. For that, you can overwrite...

@sandrooco in which next-translate & next-translate-plugin version?

Would be great if you create a reproducible example in a repo 😊 in this way we can investigate if this problem is related to the next-translate library or not....

Try: - `next-translate` - version [**`2.3.0-canary.3`**](https://github.com/aralroca/next-translate/releases/tag/2.3.0-canary.3) - `next-translate-plugin` - version [**`2.3.0-canary.6`**](https://github.com/aralroca/next-translate-plugin/releases/tag/2.3.0-canary.6) (requires Next.js 13)

We are investigating a better way to fix that, because now i18n has some trobles with the middleware (issue https://github.com/vercel/next.js/issues/49883), but for now can be solved adding a `app/route.(js|ts)` file:...