use-context-selector
redux-toolkit
use-context-selector | redux-toolkit | |
---|---|---|
27 | 287 | |
2,481 | 10,405 | |
- | 0.6% | |
6.5 | 9.8 | |
about 15 hours ago | 7 days ago | |
TypeScript | TypeScript | |
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.
use-context-selector
-
Having too many contexts - is it a problem?
Use jotai, or as someone else mentioned, zustand. React Context out of the box requires a very deliberate mental model due to a lack of tooling around selecting slices of state. This is why packages like react-context-selector exist: https://github.com/dai-shi/use-context-selector
-
Truly the best time to be a cs student
Unless I've missed it, context doesn't have selector IIRC. You'd have to use a third party solution useContextSelector
-
use-next-context: Performance-optimized React Context API.
How does this differ from https://github.com/dai-shi/use-context-selector?
-
Tips for managing and organizing complex state with React context
you can always split out context state or use a library to help with rerender issues like https://github.com/dai-shi/use-context-selector, or just switch to jotai or something else if you want something more ergonomic or better design patterns.
-
ReactJs - Useless re-renders when a context changes - HOW TO SOLVE IT ?
If you don't want to swap out useContext, you could always use useContextSelector, which helps you limit what props in the context should rerender the component.
-
React I Love You, But You're Bringing Me Down
I wouldn't call this easy
-
is Redux the first state management library you'll advise beginners to learn these days?
It wouldn't be clear to anyone learning Context API either. At least, not using official docs. Because Context API is not supposed for state management, and if you for some unknown reasons try to roll your own state management on top of it, you have to use tricky libraries to work around the issues resulting from such abuse.
-
What are some React Tricks/Tips for React Devs?
Any time anything in the context changes, any component that is consuming it will re-render. If you use it for frequently changed values, this library is needed to reduce unnecessary re-renders.
-
Surprising Performance Lessons from React Microfrontends in Production
Use of this implementation of useContextSelector
-
Inflist, an experiment using PureScript and React
Another technology I use regularly is Redux. But this time I wanted to manage the global state in a simpler and clearer way just using React hooks. I decided to go with a simple useReducer combined with theuseContextSelector hook which will avoid the whole application’s re-render caused by the native useContext hook.
redux-toolkit
-
Copilot: Weapon For Laid Back Developers
In my example I am using Redux Toolkit and I got a prompt for actions to login and logout the user. If I need more functions, I can simply start typing the name, and Copilot provides the completion. For instance, in the example, I'm adding a function to update the user. And of course at the end of the file it suggests the exports.
-
Streamlining State Management with Redux Toolkit
Check out the official documentation.
-
Next.js Weekly #34: StyleX, Self-Healing URLs, AuthKit, Scaleable TailwindCSS, Layouts vs Templates, Faster Next.js Websites [👇 all links in the comments]
Redux Toolkit 2.0
-
This Month in React Nov 2023 – Redux Toolkit 2.0, Kent v Lee, Prettier bounty
Redux Toolkit 2.0 is almost here! Hopefully shipping by this weekend :) Migration page
- 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
I am _thrilled_ to announce that:
Redux Toolkit 2.0 is LIVE!!!
- https://github.com/reduxjs/redux-toolkit/releases/tag/v2.0.0
This major version has new features, faster perf, smaller bundle size, and removes deprecated options.
It's accompanied by majors for all our Redux family packages
## RTK 2.0:
- a new `combineSlices` method for lazy-loading reducers - Updates to `createSlice` to include a `selectors` field and allow defining thunks inside
- Immer 10 w/ faster updates
- Removal of deprecated options
See the migration guide:
- https://redux.js.org/usage/migrations/migrating-rtk-2
All of the Redux libraries now have modernized packaging with full ESM/CJS compat. They also ship modern JS (no transpiling for IE11), which means smaller bundle sizes.
We've also done byte-shaving work to shrink the bundles (extracting error messages, de-duping imports)
## Redux core 5.0:
- The TS conversion we did in 2019!
- Action types _must_ be strings
- `UnknownAction` as the default action type
- Better preloaded state types
- Internal subscription improvements
- Still marks `createStore` as deprecated!
- https://github.com/reduxjs/redux/releases/tag/v5.0.0
## React-Redux 9.0:
- *Now requires React 18 and RTK 2.0 / Redux 5.0*
-
Blogged Answers: My Experience Modernizing Packages to ESM
Oh hey, that's my post!
(yes I spend too much time refreshing HN :) )
FWIW I did end up with a packaging combination that seems to work sufficiently. I never did fix the "FalseCJS" issue that `are-the-types-wrong` is detecting. I played with double-emitting TS typedefs, and the `tsup` tool _does_ actually have support for that now (added by Andrew Branch from the TS team). So it might be more feasible now. But ultimately I decided I was tired of messing with packaging setup and that what I've got is good enough. (hopefully)
We're actually about to launch Redux Toolkit 2.0 and Redux 5.0 this week, assuming the last couple pieces come together. Here's the latest RCs - you can see the current `package.json` files in there:
- https://github.com/reduxjs/redux-toolkit/releases/tag/v2.0.0...
- https://github.com/reduxjs/redux/releases/tag/v5.0.0-rc.1
-
Setting up Redux Persist with Redux Toolkit in React JS
However, Redux, or pure Redux to be specific, can be quite verbose and boilerplate-heavy. It requires a significantly lengthy setup, which is where Redux Toolkit comes in handy, offering a simplified and more efficient way to set up and manage state in your React applications.
-
44 React Frontend Interview Questions
State manager is a tool or library that helps manage the state of an application. It provides a centralized store or container for storing and managing data that can be accessed and updated by different components in the application. A state manager solves several problems. Firstly, it is a good practice to separate data and the logic related to it from components. Secondly, when using local state and passing it between components, the code can become convoluted due to the potential for deep nesting of components. By having a global store, we can access and modify data from any component. Alongside React Context, Redux or MobX are commonly used as state management libraries. Learn more Learn more
What are some alternatives?
zustand - 🐻 Bear necessities for state management in React
redux-saga - An alternative side effect model for Redux apps
reselect - Selector library for Redux
Next.js - The React Framework
redux-thunk - Thunk middleware for Redux
react-tracked - State usage tracking with Proxies. Optimize re-renders for useState/useReducer, React Redux, Zustand and others.
next-redux-wrapper - Redux wrapper for Next.js
formik - Build forms in React, without the tears 😭 [Moved to: https://github.com/jaredpalmer/formik]
vite - Next generation frontend tooling. It's fast!
why-did-you-render - why-did-you-render by Welldone Software monkey patches React to notify you about potentially avoidable re-renders. (Works with React Native as well.)
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]