Aral Roca Gomez
Aral Roca Gomez
I reopen because 1.3.2 causes conflicts and I revert it in 1.3.3. So now this issue should be fixed with a different approach.
Related: https://github.com/vinissimus/next-translate/issues/769
How did you solve to use `/, /login, /account` for each language instead of ` /de/login/ ...`? This is not directly supported (we are using [Next.js i18n routing](https://nextjs.org/docs/advanced-features/i18n-routing) behind) so...
Also if you want a better language detection way you can use this feature: https://nextjs.org/docs/advanced-features/i18n-routing#prefixing-the-default-locale
This warning in `getInitialProps` will be solved after this PR will be merged on Next.js core: https://github.com/vercel/next.js/pull/21930
@sigginjals don't you use the Webpack loader we provide? Are you using `loadNamespaces` instead? If this is the case, I understand is a thing to improve in the documentation. However,...
@Iliyass The only thing it does is to use the JSONs where you have the translations to look at the value, using the key. It should not be expensive, besides...
how much cpu and which pages spend more? the `/confirm/[token]` and `password-reset/[key]`? And it happens when downloading the translations or when translating? can you try with a blank page to...
It seems strange, why do you think it is the fault of this library?
I don't know how the isFallback works underneath, so I'll have to investigate. Thank you for reporting it @alex-ragin