react-globalize VS react-i18next

react-globalize

We haven't tracked posts mentioning react-globalize yet.
Tracking mentions began in Dec 2020.

react-i18next

• A brief history of web development. And why your framework doesn't matter
  4 projects | news.ycombinator.com | 29 Apr 2024

  > 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
  3 projects | dev.to | 13 Dec 2023

  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
  22 projects | dev.to | 14 Nov 2023

  react-i18next

• React Ecosystem in 2024
  22 projects | dev.to | 16 Oct 2023

  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
  3 projects | dev.to | 20 Aug 2023

  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
  9 projects | dev.to | 3 Aug 2023

  Website: https://react.i18next.com/

• Is it a good practice to centralized messages file
  1 project | /r/reactjs | 10 Jul 2023

  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.
  2 projects | /r/swift | 28 Jun 2023

  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
  6 projects | dev.to | 22 Jun 2023

  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.
  15 projects | dev.to | 17 Jun 2023

  react-i18next