react-i18next VS transloco

In a recent project I've been using react-i18next so I'll use its syntax for the examples, but pretty much every library works similarly.

react-i18next

i18next - You can find documentation and resources for using i18next at react.i18next.com. i18next is a popular internationalization framework for JavaScript, including React. It provides a comprehensive solution for handling translations, formatting, and more.

So far, we’ve been using a utility createLocalizedString to create and use the LocalizedString type. This utility is only really practical in unit tests. For real applications, we’ll want to use a translation function from react-i18next or next-i18next to do the heavy lifting. Then we just wrap the translation functions that are provided in order to use our type:

Website: https://react.i18next.com/

If you are talking about handling translations for your application, take a look at https://react.i18next.com/

I will be supporting Korean as a part of the beta. I have to look deeper into https://react.i18next.com/ in order to understand what it provides. My goal is for engineers to be able to click a single button and have localizations always up to date in their codebase, not delaying shipping a new version or having to even think about it.

With the new react-i18next version, when loading multiple namespaces, t function will infer and accept the keys for the first namespace. So this pattern is now accepted:

react-i18next

In this article I will show you how to translate your React app with React-i18next and give a few examples that you may find useful!

Some libraries support ways to handle missing translations (e.g., TranslocoMissingHandler from Transloco or MissingTranslationHandler   from ngx-translate). So that's a way to find out any missing translations, but that's quite manual because you have to go over every part of the served application.

For Svelte.. not sure if there's a best package.

[0] https://github.com/ngneat/transloco

Transloco 4.3: ChangeLog

We migrated from ngx-translate to Transloco ~2 years ago and it was quite painless. They have nice migration section for ngx-translate

You can take a look at Transloco. We use it all our projects.

I find Transloco a lot easier to work with compared to lokalize: https://ngneat.github.io/transloco/

I'd recommend https://ngneat.github.io/transloco/

There are a lot of tools available, but many depend on your budget. I personally enjoy Transloco.

ngx-translate is in maintenance mode and won't be develop any further (see https://github.com/ngx-translate/core/issues/783). I would highly recommend to use Transloco instead (https://ngneat.github.io/transloco/). It has same functionality as ngx-translate. Last time I checked ngx-translate doesn't actually lazyLoad translations properly but Transloco does.