transloco
react-i18next
transloco | react-i18next | |
---|---|---|
15 | 71 | |
1,940 | 8,959 | |
1.0% | 1.0% | |
9.0 | 8.8 | |
7 days ago | 15 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.
transloco
-
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.
-
Internationalization best practices for front-end developers
For Svelte.. not sure if there's a best package.
[0] https://github.com/ngneat/transloco
-
Episode 23/23: Hydration in Angular, Angular Community Meetup
Transloco 4.3: ChangeLog
-
Angular 16 Unveiled: Discover the Top 7 Features
We migrated from ngx-translate to Transloco ~2 years ago and it was quite painless. They have nice migration section for ngx-translate
-
Is the official angular/@localize i18n lib really the go to for localization?
You can take a look at Transloco. We use it all our projects.
-
Translate or Localize for a new web project
I find Transloco a lot easier to work with compared to lokalize: https://ngneat.github.io/transloco/
-
is it possible to serve locales based on browser language setting?
I'd recommend https://ngneat.github.io/transloco/
- Ng-News: Issue 22/12
-
How to use Angulars i18n in ongoing development?
There are a lot of tools available, but many depend on your budget. I personally enjoy Transloco.
-
Internationalization file maintenance for lazy loaded modules - Built in module
ngx-translate is in maintenance mode and won't be develop any further (see https://github.com/ngx-translate/core/issues/783). I would highly recommend to use Transloco instead (https://ngneat.github.io/transloco/). It has same functionality as ngx-translate. Last time I checked ngx-translate doesn't actually lazyLoad translations properly but Transloco does.
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?
ngx-translate-messageformat-compiler - Advanced pluralization (and more) for ngx-translate, using standard ICU syntax which is compiled with the help of messageformat.js.
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.
angular-i18n-example - Angular internationalization example with @angular/localize
jsLingui - ๐ ๐ A readable, automated, and optimized (3 kb) internationalization for JavaScript
core - The internationalization (i18n) library for Angular
Angular - Deliver web apps with confidence ๐
nextjs-monorepo-example - Collection of monorepo tips & tricks
i18n - A set of functions to support multiple languages/cultures in a browser or Node.js.
react-globalize - Bringing the i18n functionality of Globalize, backed by CLDR, to React