use-context-selector
rfcs
Our great sponsors
use-context-selector | rfcs | |
---|---|---|
27 | 98 | |
2,467 | 5,391 | |
- | 0.9% | |
6.0 | 2.9 | |
about 1 month ago | 4 months ago | |
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.
rfcs
-
React Labs: What We've Been Working On – February 2024 – React Compiler
Examples from the conversations of that time:
> ...we want closures to capture the values we rendered with, and to keep "seeing" those values forever. That's really important for concurrent mode where a notion of current value doesn't really exist. Hooks design models a component as being in many non-clashing states at the same time, instead of switching the "current" state (which is what classes model well). People don't really need to think about these details, but they're motivating the design a lot. [0]
> In Concurrent Mode, render may run more then one time, and since this in a class is mutable, renders that should be the same may not be. [1]
[0] - https://github.com/reactjs/rfcs/pull/68#issuecomment-4778866...
[1] - https://tkplaceholder.io/why-function-components-fit-react-b...
- A modest request: How do you fetch data in React 18+ WITHOUT a third party dependency?
-
Optimizing performance: how our extension became lightning fast
There are multiple names for this hook. You can find the documentation under the names useEvent or useEffectEvent.
-
The Sisyphean Quest for Web Performance
-https://www.patterns.dev/ -https://github.com/reactjs/rfcs/blob/main/text/0188-server-components.md -https://dev.to/this-is-learning/qwik-the-post-modern-framework-3c5o -https://dev.to/this-is-learning/astro-framework-169m -https://developers.google.com/web/updates/2019/02/rendering-on-the-web -https://web.dev/vitals/
- Why Do I Need RSC(react server components) if I Already Have Remix
-
Declaring JSX types in TypeScript 5.1
However, in React, function components can return a ReactNode. This type includes number | string | Iterable | undefined and will likely also include Promise( in the future.
-
Is ESLint Exhaustive Deps a bad rule (sometimes)?
I was also hoping that useEvent would eliminate some weird dependency cases, who knows when that will actually happen (https://github.com/reactjs/rfcs/pull/220).
-
Returning to React and looking for modern expert to sanity check
Given a lot of unknowns on SSR and ReactEng working on RSC it feels like the wrong move to use next.js and I should just use normal react. For basic react is create react app the way to go or vite?
-
Server Components vs. SSR in Next.js
As mentioned before, Next.js takes a stance of treating every component as a Server Component by default. If you want to use a Client Component, you'll need to annotate the file with use client; directive at the top of the component file.
-
Is it a bad idea to use the experimental "/app" directory in a professional project?
Use client is actually a React convention for what it’s worth. https://github.com/reactjs/rfcs/pull/227
What are some alternatives?
zustand - 🐻 Bear necessities for state management in React
server - Tolgee is translation management cloud platform made for translating modern web applications. It works great with JS frameworks like React, Angular, Vue and others. [Moved to: https://github.com/tolgee/tolgee-platform]
reselect - Selector library for Redux
react-refresh-webpack-plugin - A Webpack plugin to enable "Fast Refresh" (also previously known as Hot Reloading) for React components.
Next.js - The React Framework
react-18 - Workgroup for React 18 release.
react-tracked - State usage tracking with Proxies. Optimize re-renders for useState/useReducer, React Redux, Zustand and others.
craco - Create React App Configuration Override, an easy and comprehensible configuration layer for Create React App.
formik - Build forms in React, without the tears 😭 [Moved to: https://github.com/jaredpalmer/formik]
react-redux - Official React bindings for Redux
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.)
valtio - 💊 Valtio makes proxy-state simple for React and Vanilla