Last updated 4 months ago


For NPM users

$ npm install --save redux-actions

For Yarn users

$ yarn add redux-actions

For UMD users

The UMD build exports a global called window.ReduxActions if you add it to your page via a <script> tag. We don’t recommend UMD builds for any serious application, as most of the libraries complementary to Redux are only available on npm.

Vanilla Counter

We are going to be building a simple counter, I recommend using something like jsfiddle or codepen or codesandbox if you would like to follow along, that way you do not need a complicated setup to grasp the basics of redux-actions.

To begin we are going to need some scaffolding so here is some HTML to get started with. You may need to create a new file called main.js depending on where you are trying to set this tutorial up.

<!doctype html>
<meta charset="utf-8"/>
<script src="https://unpkg.com/redux@latest/dist/redux.js"></script>
<script src="https://unpkg.com/redux-actions@latest/dist/redux-actions.js"></script>
<button id="increment">INCREMENT</button>
<button id="decrement">DECREMENT</button>
<div id="content" />
<script src="main.js"></script>

Now that we are ready to write some JS let us create our default state for our counter.

const defaultState = { counter: 0 };

Now if we want to see our default state we need to render it. Lets get a reference to our main content and render our default state into the html.

const content = document.getElementById('content');
const render = () => {
content.innerHTML = defaultState.counter;

With our default state and renderer in place we can start to use our libraries. redux and redux-actions can be found via the globals window.Redux and window.ReduxActions. Okay enough setup lets start to make something with redux!

We are going to want a store for our defaultState. We can create one from redux using createStore.

const { createStore } = window.Redux;

We are going to want to create our first action and handle that action.

const { createAction, handleAction } = window.ReduxActions;

Next lets create our first action, 'increment', using createAction.

const increment = createAction('INCREMENT');

Next we are going to handle that action with handleAction. We can provide it our increment action to let it know which action to handle, a method to handle our state transformation, and the default state.

const reducer = handleAction(
(state, action) => ({
counter: state.counter + 1

handleAction produced a reducer for our redux store. Now that we have a reducer we can create a store.

const store = createStore(reducer, defaultState);

Now that we have a store, we can rewrite our render method to use it instead of the defaultState. We also want to subscribe our render to any changes the store might have for us.

const render = () => {
content.innerHTML = store.getState().counter;

We are ready to dispatch an action. Lets create an event listener for our increment button that will dispatch our increment action creator when clicked.

document.getElementById('increment').addEventListener('click', () => {

If you try to click the increment button you should see the value is now going up by one on each click.

We have one button working, so why don't we try to get the second one working by creating a new action for decrement.

const decrement = createAction('DECREMENT');

Instead of using handleAction like we did for increment, we can replace it with our other tool handleActions which will let us handle both increment and decrement actions.

const { createAction, handleActions } = window.ReduxActions;
const reducer = handleActions(
[increment]: state => ({ ...state, counter: state.counter + 1 }),
[decrement]: state => ({ ...state, counter: state.counter - 1 })

Now when we add a handler for dispatching our decrement action we can see both increment and decrement buttons now function appropriately.

document.getElementById('decrement').addEventListener('click', () => {

You might be thinking at this point we are all done. We have both buttons hooked up, and we can call it a day. Yet we have much optimizing to do. redux-actions has other tools we have not yet taken advantage of. So lets investigate how we can change the code to use the remaining tools and make the code less verbose.

We have declarations for both increment and decrement action creators. We can modify these lines from using createAction to using createActions like so.

const { createActions, handleActions } = window.ReduxActions;
const { increment, decrement } = createActions('INCREMENT', 'DECREMENT');

We can still do better though. What if we want an action like 'INCREMENT_FIVE'? We would want to be able to create variations of our existing actions easily. We can abstract our logic in the reducer to our actions, making new permutations of existing actions easy to create.

const { increment, decrement } = createActions({
INCREMENT: (amount = 1) => ({ amount }),
DECREMENT: (amount = 1) => ({ amount: -amount })
const reducer = handleActions(
[increment]: (state, { payload: { amount } }) => {
return { ...state, counter: state.counter + amount };
[decrement]: (state, { payload: { amount } }) => {
return { ...state, counter: state.counter + amount };

Now that we have moved our logic, our reducers are looking identical. If only we could combine them somehow. Well we can! combineActions can be used to reduce multiple distinct actions with the same reducer.

const { createActions, handleActions, combineActions } = window.ReduxActions;
const reducer = handleActions(
[combineActions(increment, decrement)]: (
{ payload: { amount } }
) => {
return { ...state, counter: state.counter + amount };

We have finally used all of the tools that redux-actions has to offer. Concluding our vanilla tutorial. This doesn't mean you don't have more to learn though. Much more can be accomplished using these tools in many ways, just head on over to the API Reference to begin exploring what else redux-actions can do for you.