App Router - i18n with MongoDB
Unanswered
indymaat posted this in #help-forum
indymaatOP
Hi Guys,
I'm trying to create a internationalized NextJS 13 app. I followed https://locize.com/blog/next-13-app-dir-i18n/ successfully, translations are working. But i want to be able to manage the translations without rebuilding the application. I found https://github.com/lamualfa/i18next-node-mongodb-backend-next that actually integrates flawlessly with the server side i18n implementation. However the client side is not able to use that backend as i get "Module not found: Can't resolve 'dns'" and other NodeJS packages that can be found, since the browser is not running Node. I am now at a bit of a crossroads.
1. Taking the route of the Locize blog: Is it possible to alter the translations files on the deployed NextJS13 app environment on Vercel without rebuilding the application or too much hassle?
2. Is it even possible to fetch the translations from MongoDB client side, or could/should the translations be fetched server-side and sent along with the client component?
3. Any advice on approaches here?
Thanks in advance
I'm trying to create a internationalized NextJS 13 app. I followed https://locize.com/blog/next-13-app-dir-i18n/ successfully, translations are working. But i want to be able to manage the translations without rebuilding the application. I found https://github.com/lamualfa/i18next-node-mongodb-backend-next that actually integrates flawlessly with the server side i18n implementation. However the client side is not able to use that backend as i get "Module not found: Can't resolve 'dns'" and other NodeJS packages that can be found, since the browser is not running Node. I am now at a bit of a crossroads.
1. Taking the route of the Locize blog: Is it possible to alter the translations files on the deployed NextJS13 app environment on Vercel without rebuilding the application or too much hassle?
2. Is it even possible to fetch the translations from MongoDB client side, or could/should the translations be fetched server-side and sent along with the client component?
3. Any advice on approaches here?
Thanks in advance