type-fest
react-i18next
type-fest | react-i18next | |
---|---|---|
32 | 71 | |
13,261 | 8,959 | |
- | 1.0% | |
9.0 | 8.8 | |
7 days ago | 15 days ago | |
TypeScript | JavaScript | |
Creative Commons Zero v1.0 Universal | 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.
type-fest
-
Adding type safety to object IDs in TypeScript
Related: https://github.com/sindresorhus/type-fest/blob/main/source/o...
-
Enforcing Localization through Types
Typescript doesn’t natively provide an Opaque type that we can use to define a string that has already been localized. If the data looks like a string, Typescript will consider it a string. We can however use utility types that simulate opaque types, like the Opaque definition in type-fest:
- Is there a better way to do read-only types
-
Boost Your JavaScript with JSDoc Typing
With these powerful features, you can create dynamic and expressive types. One last thing I want to mention before moving on, is that you can install libraries with which you can add more types to your project like type-fest or utility-types. These libraries contain a lot of useful types that you can use in your project.
-
Essential Code Organization Principles
Also, it’s not as restrictive as mutability tools — if you know what you are doing and want to ignore this limitation for a particular case, you can apply the -readonly modifier or the Writeable type from type-fest or ts-essentials.
-
Best practice for typing server data for get vs post in client code
Remember you can derive one type from another type so you can make sure they don't diverge. SetOptional type util
-
All JavaScript and TypeScript features of the last 3 years explained
Some folks have built whole SQL databases and DSL compilers in the TS type system. These tend to be toy projects with disclaimers not to use them. But the type system being Turing complete[0] (for better or worse), pretty much whatever you can imagine. This project[1] is one I actually return to frequently for practical ideas.
0: https://github.com/microsoft/TypeScript/issues/14833
1: https://github.com/sindresorhus/type-fest
-
Question on how to handle an object that can have different states and avoid assertions.
Have a look at SetRequired and SetOptional in type-fest
-
Preventing more parameters being passed than needed by a type definition?
Try the Exact method provided by Type Fest, looks like it does what you're looking for
-
Creating a derived type of only required parameters from a base type?
This is a fairly common scenario and available via libraries like type-fest or implementable with a couple lines of code.
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?
ts-toolbelt - 👷 TypeScript's largest type utility library
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
runtypes - Runtime validation for static types
next-i18next - The easiest way to translate your NextJs apps.
tss-react - ✨ Dynamic CSS-in-TS solution, based on Emotion
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
ts-essentials - All essential TypeScript types in one place 🤙
i18next - i18next: learn once - translate everywhere
zod - TypeScript-first schema validation with static type inference
nextjs-monorepo-example - Collection of monorepo tips & tricks
variant - Variant types in TypeScript
transloco - 🚀 😍 The internationalization (i18n) library for Angular