Me personally, if I know state rarely changes. Instances like user authentication, app theme (dark, light, or whatever), something to that effect. If I'm not mistaken, react docs recommends using a query library from now on to handle server data fetching like React-Query or RTK Query (I could be wrong!!!). I've only used React-Query, but I have used Redux ToolKit. More on reddit.com

You should ideally only use Context for sharing state which is contextual in nature. You should avoid using Context for global state. Zustand is more performant than context, lightweight, and really easy to learn. It can even be applied contextually, but it is made for global state by default. No good reason not to use it over Context. More on reddit.com

Hi, I'm a Redux maintainer. The answer is that they really are different tools :) Context is a Dependency Injection tool for a single value, used to avoid prop drilling. Redux is a tool for predictable global state management, with the state stored outside React. Note that Context itself isn't the "store", or "managing" anything - it's just a conduit for whatever state you are managing, or whatever other value you're passing through it (event emitter, etc). I wrote an extensive article specifically to answer this frequently asked question, including details about what the differences are between Context and Redux, and when to consider using either of them - I'd recommend reading through this: Why React Context is Not a "State Management" Tool (and Why It Doesn't Replace Redux) More on reddit.com

Sure. If you want to build all of the tooling that React-Redux provides yourself.

And now a rant, that isn’t aimed directly at you but at these this question in general because it gets asked all the time with 0 effort on the part of the asker:

Does no one do their research anymore before asking on this topic? Context is NOT a state manager, it is a storage solution. Your options for storing state in React are Context or hooks -thats it.

Don’t like Redux? Fine. But it’s ridiculous to ask “how can I replace this library with so many years of development by myself” without even doing a tiny bit of research as to what you’d gain or what you’d lose.

Not wanting to utilize something that is complicated is understandable. But state management as a whole is complicated and Redux is the battle cruiser of state management. You can build something simpler but don’t be surprised when it isn’t performant, buggy, scalable, or adaptable.

There are over 10 well maintained state management libraries now. A simple trip to Google would at least put you on the right track to understand what’s available and why.

There should probably be a sticky in the sidebar about this topic. There might even be already. I can’t tell you how many times I’ve answered this exact question here or on SO. People are obsessed with not using Redux.

While I’m in grandpa mode, to Mark Erickson, you’re a champ for heading up the React-Redux maintenance. It’s a fantastic library, your community involvement is so appreciated, and thank you for fielding so many low effort questions. You da man.

<Rant/>

More on reddit.com