What is redux-actions?
The redux-actions npm package provides utilities for creating and handling actions in Redux applications. It simplifies the process of defining action creators and reducers, making the code more readable and maintainable.
What are redux-actions's main functionalities?
createAction
The createAction function simplifies the creation of action creators. It takes a single argument, the action type, and returns an action creator function that can be called with a payload.
const { createAction } = require('redux-actions');
const increment = createAction('INCREMENT');
console.log(increment()); // { type: 'INCREMENT' }
console.log(increment(1)); // { type: 'INCREMENT', payload: 1 }
handleAction
The handleAction function allows you to create a reducer for a specific action type. It takes the action creator, a reducer function, and an initial state as arguments.
const { handleAction } = require('redux-actions');
const increment = createAction('INCREMENT');
const reducer = handleAction(increment, (state, action) => state + action.payload, 0);
console.log(reducer(0, increment(1))); // 1
handleActions
The handleActions function allows you to create a reducer that handles multiple action types. It takes an object mapping action creators to reducer functions and an initial state as arguments.
const { handleActions } = require('redux-actions');
const increment = createAction('INCREMENT');
const decrement = createAction('DECREMENT');
const reducer = handleActions({
[increment]: (state, action) => state + action.payload,
[decrement]: (state, action) => state - action.payload
}, 0);
console.log(reducer(0, increment(1))); // 1
console.log(reducer(1, decrement(1))); // 0
Other packages similar to redux-actions
redux-toolkit
Redux Toolkit is the official, recommended way to write Redux logic. It includes utilities to simplify common use cases like store setup, creating reducers, and writing immutable update logic. Compared to redux-actions, Redux Toolkit offers a more comprehensive set of tools and is maintained by the Redux team.
redux-saga
Redux Saga is a library that aims to make application side effects (e.g., asynchronous actions) easier to manage, more efficient to execute, and better at handling failures. While redux-actions focuses on simplifying action creation and reducers, redux-saga is more about handling complex side effects in a Redux application.
redux-thunk
Redux Thunk is a middleware that allows you to write action creators that return a function instead of an action. This can be used to delay the dispatch of an action or to dispatch only if a certain condition is met. Unlike redux-actions, which focuses on simplifying action and reducer creation, redux-thunk is more about handling asynchronous actions.
redux-actions


Flux Standard Action utilities for Redux.
Installation
npm install --save redux-actions
The npm package provides a CommonJS build for use in Node.js, and with bundlers like Webpack and Browserify. It also includes an ES modules build that works well with Rollup and Webpack2's tree-shaking.
If you don’t use npm, you may grab the latest UMD build from unpkg (either a development or a production build). 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.
Usage
createAction(type, payloadCreator = Identity, ?metaCreator)
import { createAction } from 'redux-actions';
Wraps an action creator so that its return value is the payload of a Flux Standard Action.
payloadCreator
must be a function, undefined
, or null
. If payloadCreator
is undefined
or null
, the identity function is used.
Example:
let increment = createAction('INCREMENT', amount => amount);
increment = createAction('INCREMENT');
expect(increment(42)).to.deep.equal({
type: 'INCREMENT',
payload: 42
});
If the payload is an instance of an Error
object,
redux-actions will automatically set action.error
to true.
Example:
const increment = createAction('INCREMENT');
const error = new TypeError('not a number');
expect(increment(error)).to.deep.equal({
type: 'INCREMENT',
payload: error,
error: true
});
createAction
also returns its type
when used as type in handleAction
or handleActions
.
Example:
const increment = createAction('INCREMENT');
handleAction(increment, {
next(state, action) {...},
throw(state, action) {...}
});
const reducer = handleActions({
[increment]: (state, action) => ({
counter: state.counter + action.payload
})
}, { counter: 0 });
NOTE: The more correct name for this function is probably createActionCreator()
, but that seems a bit redundant.
Use the identity form to create one-off actions:
createAction('ADD_TODO')('Use Redux');
metaCreator
is an optional function that creates metadata for the payload. It receives the same arguments as the payload creator, but its result becomes the meta field of the resulting action. If metaCreator
is undefined or not a function, the meta field is omitted.
createActions(?actionMap, ?...identityActions)
import { createActions } from 'redux-actions';
Returns an object mapping action types to action creators. The keys of this object are camel-cased from the keys in actionMap
and the string literals of identityActions
; the values are the action creators.
actionMap
is an optional object and a recursive data structure, with action types as keys, and whose values must be either
- a function, which is the payload creator for that action
- an array with
payload
and meta
functions in that order, as in createAction
meta
is required in this case (otherwise use the function form above)
- an
actionMap
identityActions
is an optional list of positional string arguments that are action type strings; these action types will use the identity payload creator.
const { actionOne, actionTwo, actionThree } = createActions({
ACTION_ONE: (key, value) => ({ [key]: value }),
ACTION_TWO: [
(first) => [first],
(first, second) => ({ second })
],
}, 'ACTION_THREE');
expect(actionOne('key', 1)).to.deep.equal({
type: 'ACTION_ONE',
payload: { key: 1 }
});
expect(actionTwo('first', 'second')).to.deep.equal({
type: 'ACTION_TWO',
payload: ['first'],
meta: { second: 'second' }
});
expect(actionThree(3)).to.deep.equal({
type: 'ACTION_THREE',
payload: 3,
});
If actionMap
has a recursive structure, its leaves are used as payload and meta creators, and the action type for each leaf is the combined path to that leaf:
const actionCreators = createActions({
APP: {
COUNTER: {
INCREMENT: [
amount => ({ amount }),
amount => ({ key: 'value', amount })
],
DECREMENT: amount => ({ amount: -amount })
},
NOTIFY: [
(username, message) => ({ message: `${username}: ${message}` }),
(username, message) => ({ username, message })
]
}
});
expect(actionCreators.app.counter.increment(1)).to.deep.equal({
type: 'APP/COUNTER/INCREMENT',
payload: { amount: 1 },
meta: { key: 'value', amount: 1 }
});
expect(actionCreators.app.counter.decrement(1)).to.deep.equal({
type: 'APP/COUNTER/DECREMENT',
payload: { amount: -1 }
});
expect(actionCreators.app.notify('yangmillstheory', 'Hello World')).to.deep.equal({
type: 'APP/NOTIFY',
payload: { message: 'yangmillstheory: Hello World' },
meta: { username: 'yangmillstheory', message: 'Hello World' }
});
When using this form, you can pass an object with key namespace
as the last positional argument, instead of the default /
.
handleAction(type, reducer | reducerMap = Identity, defaultState)
import { handleAction } from 'redux-actions';
Wraps a reducer so that it only handles Flux Standard Actions of a certain type.
If a reducer
function is passed, it is used to handle both normal actions and failed actions. (A failed action is analogous to a rejected promise.) You can use this form if you know a certain type of action will never fail, like the increment example above.
Otherwise, you can specify separate reducers for next()
and throw()
using the reducerMap
form. This API is inspired by the ES6 generator interface.
handleAction('FETCH_DATA', {
next(state, action) {...},
throw(state, action) {...}
}, defaultState);
If either next()
or throw()
are undefined
or null
, then the identity function is used for that reducer.
If the reducer argument (reducer | reducerMap
) is undefined
, then the identity function is used.
The third parameter defaultState
is required, and is used when undefined
is passed to the reducer.
handleActions(reducerMap, defaultState)
import { handleActions } from 'redux-actions';
Creates multiple reducers using handleAction()
and combines them into a single reducer that handles multiple actions. Accepts a map where the keys are passed as the first parameter to handleAction()
(the action type), and the values are passed as the second parameter (either a reducer or reducer map). The map must not be empty.
The second parameter defaultState
is required, and is used when undefined
is passed to the reducer.
(Internally, handleActions()
works by applying multiple reducers in sequence using reduce-reducers.)
Example:
const reducer = handleActions({
INCREMENT: (state, action) => ({
counter: state.counter + action.payload
}),
DECREMENT: (state, action) => ({
counter: state.counter - action.payload
})
}, { counter: 0 });
combineActions(...types)
Combine any number of action types or action creators. types
is a list of positional arguments which can be action type strings, symbols, or action creators.
This allows you to reduce multiple distinct actions with the same reducer.
const { increment, decrement } = createActions({
INCREMENT: amount => ({ amount }),
DECREMENT: amount => ({ amount: -amount }),
})
const reducer = handleAction(combineActions(increment, decrement), {
next: (state, { payload: { amount } }) => ({ ...state, counter: state.counter + amount }),
throw: state => ({ ...state, counter: 0 }),
}, { counter: 10 })
expect(reducer(undefined, increment(1)).to.deep.equal({ counter: 11 })
expect(reducer(undefined, decrement(1)).to.deep.equal({ counter: 9 })
expect(reducer(undefined, increment(new Error)).to.deep.equal({ counter: 0 })
expect(reducer(undefined, decrement(new Error)).to.deep.equal({ counter: 0 })
Here's an example using handleActions
:
const { increment, decrement } = createActions({
INCREMENT: amount => ({ amount }),
DECREMENT: amount => ({ amount: -amount })
});
const reducer = handleActions({
[combineActions(increment, decrement)](state, { payload: { amount } }) {
return { ...state, counter: state.counter + amount };
}
}, { counter: 10 });
expect(reducer({ counter: 5 }, increment(5))).to.deep.equal({ counter: 10 });
expect(reducer({ counter: 5 }, decrement(5))).to.deep.equal({ counter: 0 });
expect(reducer({ counter: 5 }, { type: 'NOT_TYPE', payload: 1000 })).to.equal({ counter: 5 });
expect(reducer(undefined, increment(5))).to.deep.equal({ counter: 15 });
Usage with middleware
redux-actions is handy all by itself, however, its real power comes when you combine it with middleware.
The identity form of createAction
is a great way to create a single action creator that handles multiple payload types. For example, using redux-promise and redux-rx:
const addTodo = createAction('ADD_TODO');
handleAction('ADD_TODO', (state = { todos: [] }, action) => ({
...state,
todos: [...state.todos, action.payload]
}));
addTodo('Use Redux')
addTodo(Promise.resolve('Weep with joy'));
addTodo(Observable.of(
'Learn about middleware',
'Learn about higher-order stores'
)).subscribe();
See also
Use redux-actions in combination with FSA-compliant libraries.