i18n-js
react-i18next
Our great sponsors
i18n-js | react-i18next | |
---|---|---|
4 | 70 | |
3,741 | 8,934 | |
- | 1.5% | |
5.1 | 8.9 | |
about 2 months ago | 26 days ago | |
Ruby | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
i18n-js
-
How to add internalization/localization to an app name in React Native
I'm using expo-localization, which uses i18n-js to localise my app fully except for the app name.
-
I18N in the Multiverse of Formats
The origin of this format start Ruby. The i18n-js format is a direct export of translations defined by Ruby on Rails. To export the translations, a Ruby gem can be used, that's completely disconnected from Rails and that can be used for the solely purpose of exporting the translations, even if your project is written in a different language. For JavaScript there's a companion JavaScript package. It comes bundled with all base translations made available by rails-i18n. Base translations allow formatting date, numbers, and sentence connectors, among other things.
-
A new way to handle Translations in React based applications
In most packages (i18next, i18n-js), the approach used to access translations is as follows:
-
Internationalization with Rails and i18n-js
I was working on an app built with React on Rails. Most of the pages were written in React, but some pages were written in and rendered from the Rails views. This meant that I needed to figure out a way to provide translations on both the backend and the frontend. I searched for articles and tutorials, but I couldn’t find one that was solving the same problem I had. I found a lot of tutorials on “i18n-ing” Rails apps, and some on Rails and Javascript, but not on Rails and React. After spending some time researching, I decided to try rails-i18n and i18n-js gems.
react-i18next
-
Pains and solutions in localization for the web
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.
-
45 NPM Packages to Solve 16 React Problems
react-i18next
-
React Ecosystem in 2024
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.
-
Enforcing Localization through Types
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:
-
5 Not-So-Typical React Libraries for an Outstanding Project
Website: https://react.i18next.com/
-
Is it a good practice to centralized messages file
If you are talking about handling translations for your application, take a look at https://react.i18next.com/
-
Looking for a few iOS devs that are interested in getting their apps localized.
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.
-
Supercharge Your TypeScript App: Mastering i18next for Type-Safe Translations
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 Ecosystem in 2023.
react-i18next
-
App translation with 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!
What are some alternatives?
fluent.js - JavaScript implementation of Project Fluent
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
i18next - i18next: learn once - translate everywhere
next-i18next - The easiest way to translate your NextJs apps.
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
rails-i18n - Repository for collecting Locale data for Ruby on Rails I18n as well as other interesting, Rails related I18n stuff
Simple-File-Manager - Easy app for managing your files without ads, respecting your privacy & security
nextjs-monorepo-example - Collection of monorepo tips & tricks
transloco - 🚀 😍 The internationalization (i18n) library for Angular
react-globalize - Bringing the i18n functionality of Globalize, backed by CLDR, to React