use-context-selector
redux
Our great sponsors
use-context-selector | redux | |
---|---|---|
27 | 268 | |
2,467 | 60,454 | |
- | 0.3% | |
6.0 | 9.0 | |
about 1 month ago | 9 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
-
A Comprehensive Guide to React State Management
Redux
-
Full Stack Web Development Concept map
redux - Redux is a key tool used in managing state across an application. This can be used with any web technology including React, Vue and Angular docs
-
State Management Nx React Native/Expo Apps with TanStack Query and Redux
Redux is a client-state library.
- Redux 101
-
The 20 most used React libraries
react-redux: A powerhouse for efficient state management and data flow control. Learn more
-
React State Management in 2024
Reducer-based: requires dispatching actions to update a big centralised state, often called a “single source of truth”. In this group, we have Redux and Zustand.
- 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*
-
HTML Data Attributes: One of the Original State Management Libraries
DEV is a Rails monolith, which uses Preact in the front-end using islands architecture. The reason why I mention all this is that it's not a full-stack JavaScript application, and there is no state management library like Redux or Zustand in use. The data store, for the most part on the front end, is all data attributes.
-
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
What are some alternatives?
zustand - 🐻 Bear necessities for state management in React
reselect - Selector library for Redux
remix - Build Better Websites. Create modern, resilient user experiences with web fundamentals.
Next.js - The React Framework
SWR - React Hooks for Data Fetching
react-tracked - State usage tracking with Proxies. Optimize re-renders for useState/useReducer, React Redux, Zustand and others.
valtio - 💊 Valtio makes proxy-state simple for React and Vanilla
formik - Build forms in React, without the tears 😭 [Moved to: https://github.com/jaredpalmer/formik]
swift-composable-architecture - A library for building applications in a consistent and understandable way, with composition, testing, and ergonomics in mind.
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]