core
react-i18next
core | react-i18next | |
---|---|---|
27 | 71 | |
4,467 | 8,942 | |
0.5% | 0.8% | |
1.5 | 8.8 | |
2 months ago | 10 days ago | |
TypeScript | 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.
core
- Support for 40 locales on angular 17 standalone - how?
-
Coping with i18n
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.
-
Differences ngx-translate vs i18n
ngx-translate
-
Angular 16 Unveiled: Discover the Top 7 Features
It was rather painless. We are using ngx-translate which seems dead at this point but works fine in 16 (seems to have gotten a recent commit).
- Angular 6 - i18n vs. ngx-translate
-
migrating old project to angular, need advice and recommendation on best practices
The problem with Angular 15 was the Ivy engine. And it wasn't fixed, maybe you're not affected. https://github.com/ngx-translate/core/issues/1185
-
Is the official angular/@localize i18n lib really the go to for localization?
He talks about it more here: https://github.com/ngx-translate/core/issues/783
-
i18n in angular
Ngx-translate is not updated anymore. Latest version is a year old. It's still not abandoned but it seems like the developer moved on to work on Angular i18n.
-
What's needed for ionic internationalization?
Just to refer to the original docs: https://github.com/ngx-translate/core
-
Dynamic translations in Angular made possible
One of the common pitfalls when using i18n are large translation files size and inability to split them in order to hide parts of your application from prying eyes. Some solutions like Angular built-in implementation are really powerful and SEO compatible but require a lot of preparation and do not support switching languages on the fly in development mode (which was causing troubles at least in version 9); other solutions like ngx-translate require you to install several packages and still don’t support splitting up a single language.
react-i18next
-
A brief history of web development. And why your framework doesn't matter
> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.
Would you like to elaborate on that?
In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.
For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/
Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/
Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main
Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/
React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.
Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.
-
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
What are some alternatives?
i18n-ally - 🌍 All in one i18n extension for VS Code
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
ng-zorro-antd - Angular UI Component Library based on Ant Design
next-i18next - The easiest way to translate your NextJs apps.
transloco - 🚀 😍 The internationalization (i18n) library for Angular
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
ngx-translate-messageformat-compiler - Advanced pluralization (and more) for ngx-translate, using standard ICU syntax which is compiled with the help of messageformat.js.
i18next - i18next: learn once - translate everywhere
Mycodo - An environmental monitoring and regulation system
nextjs-monorepo-example - Collection of monorepo tips & tricks
ng-conditional-validator - Angular library help you to build reactive forms dynamic validation