next-i18next: Provide i18n instance even when serverSideTranslations is not used

@skrivanos and @njarraud There is currently not a possible solution for this, I didn’t have time to work on a PR yet, however it probably would be necessary to use the overrideConfig parameter in appWithTranslation.

@dcodus You actually have to use i18next-http-backend not the middlware, you have to pass the config to appWithTranslation as overrideConfig, also don’t forget to set partialBundledLanguages to true, to allow both server and client site translations, and to check typeof window !== "undefined" before including the backend to only include it on the client side.

+1. I’d like this for cases with dynamic routes where using getStaticPaths just isn’t feasible and getServerSideProps causes unnecessary latency. For instance if you have a user specific dashboard (located at like /projects/[id]) where all data is loaded on the client.

There’s one better solution and that is for Next.js to make it possible to use getStaticProps without getStaticPaths for dynamic routes but I don’t see that happening anytime soon: https://github.com/vercel/next.js/issues/14200

Edit: https://github.com/isaachinman/next-i18next/issues/993 seems like a dupe, but was closed.

Fetching translations client side is a huge requirement for us since we load components dynamically and they define the namespaces required. It was recommended to use i18next-http-middleware https://github.com/isaachinman/next-i18next/issues/1004#issuecomment-790013130 to achieve this however i was not able to make it work by simply including it in config.use. @isaachinman Would you be able to provide more details about how this needs to be wired up? Much appreciated!

instead of require("i18next-http-backend").default write require("i18next-http-backend/cjs")

What is the current way of doing for dynamic routes that do not require getStaticProps or getServerSideProps other than for translations?

Nextjs requires to have getStaticPaths if getStaticProps is used for dynamic routes. I could use this solution with fallback: true but considering that serverSideTranslations is the only props in getStaticProps, it will build exactly the same file over and over again and I will end up with 1000s of identical pages. Am I missing something?

Thanks a million!

Feel free to work on a PR. Just bear in mind it will need test coverage. Thanks!

Right, the fallback was just an example why it would be useful to have the i18n instance available at all times.

I don’t see any reason where not having it there is better that having it there, while having it provided even without translations allows reuse of the same configuration everywhere.

I would start by enquiring on the NextJs repo, rather than fetching translations on the client side, via HTTP.

Translations through HTTP is necessary in certain situations. For example, I don’t necessarily want to preload translations for parts of the app that my users might rarely access, dynamic options with translations for select components and authentication locked translations to name a few.