Dynamic Reducers

In this lesson you will learn dynamic reducers in Redux, why it matters within code splitting, and how to use it correctly with clear, copy-ready examples.

Dynamic Reducers Overview

Dynamic Reducers is something you will reach for often in Redux. It keeps your workflow predictable and makes your intent obvious to reviewers and teammates.

When you learn dynamic reducers properly, you avoid the guesswork that leads to mistakes and rework. The example below shows the shape you will use in most real Redux projects.

import { createSlice } from '@reduxjs/toolkit';

const counterSlice = createSlice({
  name: 'counter',
  initialState: { value: 0 },
  reducers: {
    increment: (state) => { state.value += 1; },
    addBy: (state, action) => { state.value += action.payload; },
  },
});

export const { increment, addBy } = counterSlice.actions;
export default counterSlice.reducer;

createSlice generates actions and a reducer together; Immer lets you write safe 'mutating' updates.

Dynamic Reducers Example

const slice = createSlice({ name, initialState, reducers });
const store = configureStore({ reducer: { key: slice.reducer } });
// dispatch(slice.actions.something())

Start from a minimal Dynamic Reducers example and grow it only as needed.
Keep things explicit so Dynamic Reducers behaves the same for everyone on the team.
Name things clearly so teammates understand your Dynamic Reducers at a glance.
Verify Dynamic Reducers works as expected before relying on it in important work.

Redux Cheatsheet

Quick Redux Toolkit reference related to dynamic reducers.

Concept	Example	Purpose
Store	`configureStore({ reducer })`	Hold app state
Slice	`createSlice({ name, reducers })`	State + actions together
Read state	`useSelector((s) => s.x)`	Get data in components
Dispatch	`useDispatch()`	Send actions
Async	`createAsyncThunk(...)`	Handle side effects
Data fetching	`createApi(...)`	RTK Query endpoints
Derived data	`createSelector(...)`	Memoized computations

How Dynamic Reducers Works in Redux

Dynamic Reducers follows Redux's predictable data flow: components dispatch actions, reducers compute the next state from the previous state and the action, and subscribed components re-render.

createSlice generates actions and a reducer together; Immer lets you write safe 'mutating' updates.

State lives in a single, read-only store.
Actions are the only way to describe a change.
Reducers are pure functions that return the next state.
Redux Toolkit removes most boilerplate with slices and thunks.

Practical Guidance for Dynamic Reducers

In modern apps, dynamic reducers should use Redux Toolkit rather than hand-written Redux. Keep state minimal, colocate logic in slices, and use RTK Query for server data.

Concern	Recommendation
Boilerplate	Use Redux Toolkit (createSlice)
Server data	Prefer RTK Query over manual thunks
Performance	Memoize selectors with createSelector
Types	Use typed useAppSelector/useAppDispatch hooks

Common Mistakes

Copying dynamic reducers commands or snippets without understanding what each part does.
Skipping edge cases and error handling when using dynamic reducers.
Not verifying the result of dynamic reducers before moving on.
Over-complicating dynamic reducers before you actually need the extra flexibility.

Key Takeaways

Dynamic Reducers is a core part of working effectively with Redux.
Start small and keep dynamic reducers focused on a single goal.
Apply consistent patterns so dynamic reducers scales across your project.
Practise and document dynamic reducers to keep your workflow maintainable.

Pro Tip

Practise dynamic reducers on a throwaway project first. It is far cheaper to learn Redux mistakes there than on important work.