DEV Community

Cover image for I18n and React, a simple and easy solution
John B
John B

Posted on

I18n and React, a simple and easy solution

package

Internationalization can be a headache and is oftentimes heavy; both in terms of code size and overhead.

With this in mind, I wrote a very simple, lightweight package for react (7.1kB minified, no dependencies).

Unconventional features:

Backend independent

It can be linked to any backend. I assume here that the list of translations is stored somewhere on the internet (typically served from the backend).

Once loaded, the list of translations is stored in the local storage so that the application can be reloaded quickly.

Untranslated strings

I have always found it hard to know which strings were translated and which were not. With this package, we store all the untranslated strings in an array in the local storage, so that you can see at anytime all the missing strings - all you need to do is browse through the application.

Features

  • n languages
  • string interpolation
  • typescript
  • 0 dependencies
  • Built with react in mind, but can be used with any JS framework.

Get it!

Top comments (1)

Collapse
 
ars33 profile image
Арсений Попов

🔥 This is exactly what modern i18n should be! Lightweight, backend-agnostic, and developer-friendly. Love the focus on untranslated strings visibility – that's a game-changer for localization workflows.

For teams looking to take it a step further, check out G-Lang (bit.ly/3YbEtZf) – it lets you manage translations right from Google Sheets and sync them to your app via API with just 2 lines of config. No CMS bloat, no manual file updates – just seamless i18n.

Great work on the package! 🚀