Redux: A State Management Library for JS
/redux
Redux is a JavaScript library that makes state changes predictable across an entire app, built around a single store, plain-object actions, and pure reducer functions that compute the next state. Its own README frames it as worth adopting once a top-level component's state stops being enough and you need one source of truth; skip it for a small app where a couple of components already handle their own state fine.
Understanding Redux and Redux Toolkit
Redux is a JavaScript library that stores an entire application's state in a single object tree and only lets you change it by dispatching plain-object actions to pure reducer functions. That's the whole model. It works with React or, per its own README, any other view library, and runs in client, server, and native environments. Redux Toolkit is the officially recommended way to write the reducer and store setup around it.
Key Benefits of Redux for Developers
- ✓A single store holds the whole app's state as one object tree, so every component reads from the same source of truth.
- ✓State changes only happen through dispatched action objects handled by pure reducer functions, per the README's description of the data flow.
- ✓Redux Toolkit wraps the core with createSlice and configureStore, and uses the Immer library internally so reducers can write code that looks like mutation without actually mutating state.
- ✓Works with React or, per the README, any other view library, since the core itself doesn't depend on a UI framework.
- ✓The core library is small (about 2kB including dependencies, per the README), with a wider ecosystem of addons layered on top.
- ✓Runs in client, server, and native environments, per the README.
- ✓Pairs with Redux DevTools for live code editing and time-travel debugging, per the README.
When Redux Fits Your Application Needs
- •Apps where a fair amount of state changes as the app runs, and passing it down through several layers of props has stopped scaling, per the README's own framing.
- •Projects that need one single source of truth for state shared across many unrelated components, not just a couple of siblings.
- •Teams building with React via Redux Toolkit's official Vite or Next.js templates, which come preconfigured with React-Redux.
- •Codebases where reproducing a bug benefits from Redux DevTools' time-travel debugging, since every state change traces back to a dispatched action.
- •Non-React projects, since the README states Redux works with any view library, not just React.
Strengths
- ✓A single store and pure reducers make state changes traceable, since every change has to go through a dispatched action rather than an arbitrary mutation.
- ✓Redux Toolkit's createSlice and configureStore cut down the setup that older bare-Redux code needed.
- ✓The core is small (about 2kB including dependencies, per the README) yet has a wide ecosystem of addons built around it.
- ✓Two official tutorials, Essentials (top-down) and Fundamentals (bottom-up), cover both how to use Redux and how it works under the hood.
- ✓Works across client, server, and native environments and isn't tied to React, per the README.
- ✓MIT licensed, so there's no copyleft concern about shipping it inside a commercial app.
Considering When Not to Use Redux
- △The README itself says its own guidance on when to adopt Redux is subjective and vague, and directly warns against reaching for it just because someone else said you should.
- △No official React Native template exists yet; the README instead points to two community-maintained templates for React Native and Expo.
- △Small apps where only a couple of components share state may not need the extra ceremony of actions, reducers, and a store; the README's own linked essay, Dan Abramov's "You Might Not Need Redux," makes that case directly.
- △The README's install and usage examples focus on Redux Toolkit with React; using the bare redux package by itself is covered with a single install command and a pointer to the external docs site for the rest.
Getting Started with Redux Installation
For a new React plus Redux Toolkit app, the README points to the official Vite and TypeScript template via `npx degit reduxjs/redux-templates/packages/vite-template-redux my-app`, or a Next.js starting point via `npx create-next-app --example with-redux my-app`; both come with React-Redux already configured. To add Redux Toolkit to an existing project, run `npm install @reduxjs/toolkit react-redux`. If you only want the core store and reducer library without Toolkit, `npm install redux` is enough on its own. There's no official React Native template yet; the README links to two community-built ones for React Native and Expo instead. Full installation details live on the Installation docs page at redux.js.org.
Basic State Management with Redux Toolkit
The README's basic example builds a counter with Redux Toolkit's createSlice, which takes a name, an initial state, and reducer functions, then exports the generated action creators (incremented, decremented) automatically. A configureStore call turns that slice's reducer into the app's store, which you can still subscribe to and dispatch actions against directly. Inside a reducer you can write state.value += 1 as though mutating the object directly; Redux Toolkit uses the Immer library under the hood to turn that into a new immutable state object rather than an actual mutation, so the code stays short without changing Redux's underlying store, action, and reducer flow.
Exploring Alternatives to Redux
Common Questions About Redux
Redux Toolkit is Redux's official recommended way to write Redux logic. It wraps the Redux core with functions like createSlice and configureStore, builds in suggested best practices, and cuts down the setup and common mistakes that came with writing plain Redux by hand.
Redux works with view libraries other than React. Its own README states the core doesn't depend on any single UI framework, so it can pair with other view libraries the same way it pairs with React.
Redux's README points to two official tutorials: the Essentials tutorial, a top-down walkthrough using current best practices, and the Fundamentals tutorial, a bottom-up guide to the underlying mechanics, without any of the abstractions Toolkit adds on top.
Redux's own README suggests reaching for it once an app has a meaningful amount of state changing over time, needs one source of truth for that state, or has outgrown keeping everything in a single top-level component, though it calls these guidelines subjective by nature.
Redux is built to run in client, server, and native environments, according to its own README, so the same store, action, and reducer pattern isn't limited to browser-only apps.
Redux is released under the MIT license, according to its GitHub repository.
The problem it solves
Redux exists for apps where passing state down through props, or keeping everything in one top-level component, breaks down once enough different parts of the UI need to read and change the same data. The README frames this directly: once an app has a meaningful amount of data changing over time and needs one source of truth for it, ad hoc component state stops being enough, and Redux offers a single store plus a predictable action-and-reducer flow instead.
Who should try it — and who should skip
Try Redux if your app's state is shared across many components, you want every change traceable to a dispatched action, or you're building with Redux Toolkit's official templates and want the DevTools time-travel debugger. Skip it if your app only has a couple of components sharing data: the README's own linked essays, including Dan Abramov's "You Might Not Need Redux," argue against reaching for it just because it's the default choice.
Still deciding about redux?
One click hands the question to an AI along with this page — see what it says about redux.