onyxia-web VS simplelocalize-cli

On the contrary, in my experience it is the approach that scales best. (Not so )big example.

In favor of i18nifty: - typesafe-i18n translations are flat string, i18nifty on the other hand enables to involve logic and React components in your translations. You can't write this or that with typesafe-i18n for example. - i18nifty achieve the same level of type-safety without requiring you to have a process running in the background while you are coding. - In my library you have a i18n namespace by React component, in typsafe-i18n the namespace are decoupled from the component which makes it much harder to manage. See this would be a nightmare to manage if we had to create the namespace manually.

Onyxia-web is a create-react-app distributed as a Docker image.

shamless plug You can use my app for that, it doesn’t require monthly subscription. 😉

In favor of typesafe-i18n: - Offers an option for asynchronous loading of locales. It's in the roadmap for i18nifty but as of today it doesn't features it. - It's lighter 1.3Kb vs 22Kb for i18nifty (I could work on reducing the size but it isn't high in my priorities). - Support third party localisation services such as https://locize.com/ https://lokalise.com/ or https://simplelocalize.io/.

NextJS, a well-known framework among React developers, provides multiple libraries that create a very developer-friendly environment. The most popular ones are i18Next, next-translate and, our main focus in this blog post, next-18next, a translation library that does a fantastic job helping in translation management. The following blog post will show you how to set up next-i18n in your NextJS app and manage translations with SimpleLocalize. Take a look at our demo app for the reference.

own SaaS my salary is now higher than before 😌

I know the advantage of this approach is that you can do it for free, but in general you could also use something like SimpleLocalize (I’m the author, backend uses Spring and Java 18😎) You can keep translations there, auto-translate and host them on CDN. In my approach, the cool thing is that you can fix the incorrect auto-translated texts in the editor. It supports DeepL and Google Translate, there is a free forever plan and free 14-day trial.

Wow, that’s great! I was thinking that you used some kind of software like SimpleLocalize to use auto-translation. :)

Don’t implement it on your own. Use something like SimpleLocalize and use their REST API and CDN. Client will have a nice panel to edit/change translations and you will get a nice API to fetch translated content.