polyglot VS react-i18next

You'll find many code snippets below. Most of them come from the source code of Polyglot itself. This article aims to give you more explanations about that code, its purpose, and its use.

The bloat comes from a minority of package authors with attitudes like this: https://github.com/airbnb/polyglot.js/pull/150

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!