Aral Roca Gomez

@sapkra is something unfeasible because being able to overwrite the function `loadLocaleFrom`, the translations can be anywhere, in JSON or any format, inside the project, or in an external API......

@VictorAssis Are you using a HoC on the `/about.js` page? Next-translate uses `getInitialProps` as default to load the translations when there is a HoC detected (to avoid problems). https://github.com/vinissimus/next-translate/tree/1.0.1#how-are-translations-loaded You...

@VictorAssis it looks related to this issue: https://github.com/vinissimus/next-translate/issues/444 Is detecting the word [`getInitialProps` of `/about.js` file.](https://github.com/VictorAssis/next-translate-bug/blob/main/apollo-with-translate/pages/about.js#L23). This is because the `getInitialProps` detection is quite poor: - https://github.com/vinissimus/next-translate/blob/1.0.1/src/plugin/loader.ts#L85 Naturally, this needs...

@VictorAssis @CleverUpEng we did some improvements on the internal `hasHOC` helper. Is it already happening to you on [1.0.2-canary.9](https://github.com/vinissimus/next-translate/releases/tag/1.0.2-canary.9)? Thanks 🙏

This will be fixed after this PR in Next.js https://github.com/vercel/next.js/pull/21930

Should be fixed in [Next.js canary 10.2.1-canary.4](https://github.com/vercel/next.js/releases/tag/v10.2.1-canary.4) Can someone confirm it?

Okay, I noted for version 1.1. Thanks @LoganAtCrypto

@LoganAtCrypto maybe you can configure via this feature https://github.com/vinissimus/next-translate/pull/589/files

It would be nice if you could share a repo reproducing the bug so we can help 😊

@devaquila you can fix it with an environment variable indicating the path: `NEXT_TRANSLATE_PATH`. Is documented here: https://github.com/vinissimus/next-translate#12-how-to-use-next-translate-in-a-mono-repo. I close the issue. If you still having problems please comment here or...