Skip to content

ibitcy/eo-locale

Repository files navigation

build status types included

  • 💪Runs in all browsers and Node.js
  • ☎Can be used not only in React.Component but also in Vanilla JS
  • 📦Really tiny size. Calculated by size-limit and bundlephopia.
  • 📚Message format is strictly implemented by ICU standards
  • 🎓Support for 150+ languages
  • 🎉Support HTML in message. Support React Elements as variables
  • 🎢Locale data in nested JSON format are supported
  • 👫Simple. Only four components and one hook
  • ⚙️TypeScript and Flow types out of the box. Library has written on TypeScript
  • 🎄Optimized for tree shaking

Motivation

Internationalization is the process of adapting an application to work with different languages and regions. That can bring some benefits. Your target group can be broader than the one with the default language of the app. So by internationalizing an app, you may reach a bigger audience.

Internationalization it's not only about translation text. Users expect localized Dates, Number separators, Currencies.

Compare with most popular libraries

Today each dependency drags more dependencies and increases your project’s bundle size uncontrollably. But size is very important for everything that intends to work in a browser.

eo-locale is a simple library for those who care about their bundle size and client-side performance. It is fast and lightweight because:

  • built with hooks and functional components only (no classes and polyfills for them);
  • ships only a minimal amount of manually optimized algorithms;

To show you the problem that eo-locale is trying to solve, we have performed a simple benchmark (using bundlephobia.com) against popular React localization libraries:

Name Bundle size Bundle size (gzip)
eo-locale
react-intl
react-i18next
react-intl-universal
@lingui/react

Projects using eo-locale