Monorepo & shared translation files #1604
Unanswered
ThomasKuhlmann
asked this question in
Q&A
Replies: 1 comment
-
Right...bundling translations of bigger apps is a no-go (grows too big). You will have to publish your translations to some webserver or CDN and consume it from there - I guess. If you consider moving to locize in a later phase anyway - you can also reach out to me directly jamuhl@locize.com and we can see how we can help (extended trial, discount). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
I've just moved a single Vue app into a monorepo (Lerna & yarn workspaces), which has now two Vue apps, a serverless backend and a shared UI library.
So far I had kept my i18next translations in the public folder of my Vue app, and I am struggling with how to best restructure this so that all the apps and the UI library can access the code, and still benefit from lazy loading. I initially thought translations would be a package and I'll just import it, but this does seem to simply bundle all languages and namespaces and load them upfront?
Does anybody have a similar setup and could share some pointers? I am happy to move everything to a service like locise in the future, but I'd like to avoid the price tag while I am still in the pre-launch phase...
Beta Was this translation helpful? Give feedback.
All reactions