hooks
react-i18next
hooks | react-i18next | |
---|---|---|
7 | 71 | |
13,354 | 8,942 | |
0.8% | 0.8% | |
8.5 | 8.8 | |
6 days 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.
hooks
-
Can't come to a conclusion if a component is pure or not. Please make me understand.
I re-read relevant documentation many times and am very aware of what purity means. I guess what's throwing me off is that every hook library uses such implementation of usePrevious: * react-hookz * ahooks * rooks
-
Alternative libs to migrate from React to Vue (or Vue to React)
ahooks
-
Common React Design patterns: Custom Hooks
react-use * ⭐️ 29.6k / 🔽 958k ahooks * ⭐️ 9.1k / 🔽 74k awesome-react-hooks * ⭐️ 8.1k / 🔽 74k usehooks-ts * ⭐️ 1.6k / 🔽 44k react-recipes * ⭐️ 850 / 🔽 1.2k react-hanger * ⭐️ 1.8k / 🔽 3.3k
-
ahooks 3.0 is coming! a high-quality and reliable React Hooks library!
Document: https://ahooks.js.org
-
useLockFn 中 useCallback 的用途
ahooks 库里面有一个 useLockFn
- Ahooks, React hooks library from Alibaba
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?
use-between - Sharing state between React components
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
beautiful-react-hooks - 🔥 A collection of beautiful and (hopefully) useful React hooks to speed-up your components and hooks development 🔥
next-i18next - The easiest way to translate your NextJs apps.
reactfire - Hooks, Context Providers, and Components that make it easy to interact with Firebase.
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
haunted - React's Hooks API implemented for web components 👻
i18next - i18next: learn once - translate everywhere
vueuse - Collection of essential Vue Composition Utilities for Vue 2 and 3
nextjs-monorepo-example - Collection of monorepo tips & tricks
react-use - React Hooks — 👍
transloco - 🚀 😍 The internationalization (i18n) library for Angular