react-tracked
use-context-selector
react-tracked | use-context-selector | |
---|---|---|
5 | 27 | |
2,637 | 2,481 | |
- | - | |
6.7 | 6.5 | |
8 days ago | 1 day 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.
react-tracked
- My company doesn't use any state management tool. Is that bad?
-
How Valtio Proxy State Works (React Part)
Automatic render optimization is to do this automatically. Is this possible? It's possible with utilizing proxies. Proxies allow us to detect state property access. I have been working on this for years, and react-tracked is one of the resulting projects that use this technique. We have an internal library called proxy-compare.
-
React Tracked: Manage state and prevent excessive re-rendering
While in a smaller application, excessive re-rendering may be unnoticeable or have no negative impact, as your application grows, each re-render may cause delays or lags in your UI. In this tutorial, we’ll use React Tracked, a library for state usage tracking, to optimize our application’s performance by preventing unnecessary re-renders.
- React Context, All in One
-
What are Tuples and Records in JavaScript?
The best, and perhaps only approach I have found so far is react-tracked. It does some internal tracking with proxies that I don't quite understand, but it actually works as advertised with a very minimal API.
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.
What are some alternatives?
Talkr - Talkr is the lightest i18n provider for React applications. It supports Typescript, provides autocompletion, has 0 dependencies, and is very easy to use.
zustand - 🐻 Bear necessities for state management in React
proposal-record-tuple - ECMAScript proposal for the Record and Tuple value types. | Stage 2: it will change!
reselect - Selector library for Redux
rfcs - RFCs for changes to React
Next.js - The React Framework
todo-app-react - React Application that contains scenario based implementation. It covers nested routing using react-router-dom, state management using react-redux, lazy loading components, suspense api, async call using axios. please refer README.md for more details.
formik - Build forms in React, without the tears 😭 [Moved to: https://github.com/jaredpalmer/formik]
proxy-compare - Compare two objects using accessed properties with Proxy
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 - The library for web and native user interfaces.