reselect
i18next
reselect | i18next | |
---|---|---|
46 | 61 | |
18,999 | 7,413 | |
0.0% | 1.0% | |
9.6 | 9.2 | |
4 days ago | 6 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.
reselect
- Redux Toolkit 2.0: new features, faster perf, smaller bundle sizes (plus major versions for all Redux family packages!)
-
Redux Toolkit 2.0: new features, faster perf, smaller bundle sizes, and more
- Throws better errors in an RSC environment
- https://github.com/reduxjs/react-redux/releases/tag/v9.0.0
## Reselect 5.0:
- Switches to a new `weakMapMemoize` memoizer as default
- Renames `defaultMemoize` to `lruMemoize`
- Allows passing memoizer options direct to `createSelector`
- Many TS improvements
- https://github.com/reduxjs/reselect/releases/tag/v5.0.1
## Redux Thunk 3.0:
- Drops the default export and switches to named exports ( `{thunk, withExtraArgument}` )
- https://github.com/reduxjs/redux-thunk/releases/tag/v3.1.0
This has been a _huge_ year-long development effort!
We're thrilled to get these improvements out. The tooling and bundle improvements will help all users, and we think the features and TS changes will improve the Redux dev experience significantly.
Thank you SO MUCH to everyone who has contributed or helped test out the work!
Please file bug reports for the inevitable issues that pop up post-release!
but now I'm going off on a conf trip and going to take a very well-earned break from Redux work for December :)
-
45 NPM Packages to Solve 16 React Problems
reselect -> For making faster queries to store.
-
Top 7 Libraries for Blazingly Fast ReactJS Applications
Reselect solves this problem by memorizing the values and only passing what’s necessary.
-
What's the benefit of Redux?
In addition, diagnosing bugs in how data flowed through the application (where data originated from, how it was changed, etc.) was always super painful because I had to backtrack through selectors referencing selectors referencing selectors. And updating high-level selectors risked breaking something else down the line (even with 100% business logic coverage this was a problem). (This may be chalked up to improper usage of reselect, but I'm curious to hear your thoughts. Is this a common problem?)
-
20 Essential Parts Of Any Large Scale React App
reselect : Selector library to optimize your store access
-
Revolutionize Your React App with Redux: A Beginner's Guide to Simplifying State Management(PART 2)
Reselect documentation:
-
What is memoization in React
Applying memoization to TypeScript and ReactJS is relatively straightforward. There are several libraries available that provide memoization functionality, such as memoize function from Lodash, reselect or hooks from ReactJS. These libraries can be installed using NPM or Yarn and used in your TypeScript and ReactJS projects.
-
ThreeJS project wrapped in Redux for State Management
Generally, all you would need is to have your redux store provider at the very top level of your application (You could also only wrap the components that you want to have this data available to). Then, any component rendered inside that provider can get access to the redux store. The suggested approach ever since hooks were released is to use `useSelector` and `useDispatch` within your component to get the state data that you need. Using a selector library like Reselect is prevalent and keeps your data selection tidy & handles memoization for you.
-
20 Best Libraries and Tools for React Developers
Reselect is a library for creating memoized “selector” functions. Commonly used with Redux, to slice state and provide just the necessary subtree to a React component.
i18next
-
Implementing Internationalization (i18n) in Vue.js Projects
For this article, we'll leverage the 'Simple CRM' project from our previous list of projects. We'll integrate and utilize the i18n library to internationalize our application.
-
Translating zod errors with next-intl
When starting a new project with Next.js these days, next-intl and zod are my go to libraries for internationalization and schema validation, respectively. Of course, when using zod for client-facing validations I would like to translate potential error messages. The package zod-i18n can be used to achieve this for i18next, a popular alternative internationalization library. This means that by using this library as starting point one can quickly achieve zod translation with next-intl.
-
Top 20 Frontend Interview Questions With Answers
The best way to implement internationalization is to use an internationalization framework library, such as i18next. With this kind of library, you can easily handle translations and automatically display your frontend labels in the user's language. The frontend application also needs to be flexible and easily configurable so that its layout can change accordingly, reading from left to right or right to left. CSS allows this with the rtl and ltr CSS direction property.
-
Reactive translation/i18n
For reference, I am using i18next for providing translations, which is configured to use the english message string as a key for the translations and fallback to it if no translation is found in the chosen language. I also use the official svelte-i18next integration. It wraps the i18next object in a Svelte store and, among other things, provides reactivity when the language is changed.
-
Building a multilingual NextJS app using the new app directory
// app/components/BuiltInFormatsDemo.tsx 'use client'; import React from 'react'; import {useTranslation} from '../i18n/client'; import type {LocaleTypes} from '../i18n/settings'; import {useParams} from 'next/navigation'; const BuiltInFormatsDemo = () => { let locale = useParams()?.locale as LocaleTypes; const {t} = useTranslation(locale, 'built-in-demo'); return (
{/* "number": "Number: {{val, number}}", */} {t('number', { val: 123456789.0123, })} p>
{/* "currency": "Currency: {{val, currency}}", */} {t('currency', { val: 123456789.0123, style: 'currency', currency: 'USD', })} p>
{/* "dateTime": "Date/Time: {{val, datetime}}", */} {t('dateTime', { val: new Date(1234567890123), formatParams: { val: { weekday: 'long', year: 'numeric', month: 'long', day: 'numeric', }, }, })} p>
{/* "relativeTime": "Relative Time: {{val, relativetime}}", */} {t('relativeTime', { val: 12, style: 'long', })} p>
{/* "list": "List: {{val, list}}", */} {t('list', { // https://www.i18next.com/translation-function/objects-and-arrays#objects // Check the link for more details on `returnObjects` val: t('weekdays', {returnObjects: true}), })} p> div> ); }; export default BuiltInFormatsDemo;
-
Supercharge Your TypeScript App: Mastering i18next for Type-Safe Translations
As our world becomes increasingly interconnected, the development of web applications that cater to a global audience takes precedence among developers. If you're a TypeScript developer, you're likely acquainted with the advantages of static typing and the assurance it provides in your codebase. When it comes to internationalization (i18n) and localization (l10n), maintaining the same level of type safety becomes crucial. This is precisely where i18next, an influential i18n framework, enters the picture.
-
localization in nextjs13
check i18next
-
Creating Multilingual React Apps with i18n: A Step-by-Step Guide to Internationalisation
In this article, we will go over how to perform internationalisation in our react app using the i18next framework. I18next is an internationalisation framework written in JavaScript. It comes with everything you need to localise your web, desktop or mobile product such as user language detection, loading and caching translations, and file conversion etc More features can be found in their documentation. (https://www.i18next.com/)
-
Change language in a website
Luckily this is a well-solved problem: https://www.i18next.com/
-
What is the best way to handle a multi-language site?
I am so sorry for all the people using https://www.i18next.com/ and manually defining string ids. Fuck that. I will never write another message id in my life.
What are some alternatives?
recompose - A React utility belt for function components and higher-order components.
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
Immer - Create the next immutable state by mutating the current one
polyglot - Give your JavaScript the ability to speak many languages.
use-context-selector - React useContextSelector hook in userland
Screen-Translator - An Electron.js-based desktop application for automatically translating on-screen text.
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
react-i18next - Internationalization for react done right. Using the i18next i18n ecosystem.
react-redux - Official React bindings for Redux
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
effector-react - Business logic with ease ☄️
deepl-translator - This module provides promised methods for translating text using DeepL Translator (https://www.deepl.com/translator) undocumented API.