Need help with redux-thunk?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

16.7K Stars 982 Forks MIT License 126 Commits 5 Opened issues


Thunk middleware for Redux

Services available


Need anything else?

Contributors list

Redux Thunk

Thunk middleware for Redux.

GitHub Workflow Status npm version npm downloads

npm install redux-thunk

yarn add redux-thunk

Note on 2.x Update

Most tutorials today assume that you're using Redux Thunk 1.x. You may run into issues when you run their code with 2.x. If you use Redux Thunk 2.x in CommonJS environment, don’t forget to add

to your import:

- const ReduxThunk = require('redux-thunk')
+ const ReduxThunk = require('redux-thunk').default

If you used ES modules, you’re already all good:

import ReduxThunk from 'redux-thunk'; // no changes here 😀

Additionally, since 2.x, we also support a UMD build:

const ReduxThunk = window.ReduxThunk.default;

As you can see, it also requires

at the end.

Why Do I Need This?

With a plain basic Redux store, you can only do simple synchronous updates by dispatching an action. Middleware extends the store's abilities, and lets you write async logic that interacts with the store.

Thunks are the recommended middleware for basic Redux side effects logic, including complex synchronous logic that needs access to the store, and simple async logic like AJAX requests.

For more details on why thunks are useful, see:

  • Stack Overflow: Dispatching Redux Actions with a Timeout
    Dan Abramov explains the basics of managing async behavior in Redux, walking through a progressive series of approaches (inline async calls, async action creators, thunk middleware).

  • Stack Overflow: Why do we need middleware for async flow in Redux?
    Dan Abramov gives reasons for using thunks and async middleware, and some useful patterns for using thunks.

  • What the heck is a "thunk"?
    A quick explanation for what the word "thunk" means in general, and for Redux specifically.

  • Thunks in Redux: The Basics
    A detailed look at what thunks are, what they solve, and how to use them.

You may also want to read the Redux FAQ entry on choosing which async middleware to use.

While the thunk middleware is not directly included with the Redux core library, it is used by default in our



Redux Thunk middleware allows you to write action creators that return a function instead of an action. The thunk can be used to delay the dispatch of an action, or to dispatch only if a certain condition is met. The inner function receives the store methods

as parameters.

An action creator that returns a function to perform asynchronous dispatch:


function increment() { return { type: INCREMENT_COUNTER, }; }

function incrementAsync() { return (dispatch) => { setTimeout(() => { // Yay! Can invoke sync or async actions with dispatch dispatch(increment()); }, 1000); }; }

An action creator that returns a function to perform conditional dispatch:

function incrementIfOdd() {
  return (dispatch, getState) => {
    const { counter } = getState();

if (counter % 2 === 0) {


}; }

What’s a thunk?!

A thunk is a function that wraps an expression to delay its evaluation.

// calculation of 1 + 2 is immediate
// x === 3
let x = 1 + 2;

// calculation of 1 + 2 is delayed // foo can be called later to perform the calculation // foo is a thunk! let foo = () => 1 + 2;

The term originated as a humorous past-tense version of "think".


npm install redux-thunk

Then, to enable Redux Thunk, use


import { createStore, applyMiddleware } from 'redux';
import thunk from 'redux-thunk';
import rootReducer from './reducers/index';

// Note: this API requires [email protected]>=3.1.0 const store = createStore(rootReducer, applyMiddleware(thunk));


Any return value from the inner function will be available as the return value of

itself. This is convenient for orchestrating an asynchronous control flow with thunk action creators dispatching each other and returning Promises to wait for each other’s completion:
import { createStore, applyMiddleware } from 'redux';
import thunk from 'redux-thunk';
import rootReducer from './reducers';

// Note: this API requires [email protected]>=3.1.0 const store = createStore(rootReducer, applyMiddleware(thunk));

function fetchSecretSauce() { return fetch(''); }

// These are the normal action creators you have seen so far. // The actions they return can be dispatched without any middleware. // However, they only express “facts” and not the “async flow”.

function makeASandwich(forPerson, secretSauce) { return { type: 'MAKE_SANDWICH', forPerson, secretSauce, }; }

function apologize(fromPerson, toPerson, error) { return { type: 'APOLOGIZE', fromPerson, toPerson, error, }; }

function withdrawMoney(amount) { return { type: 'WITHDRAW', amount, }; }

// Even without middleware, you can dispatch an action: store.dispatch(withdrawMoney(100));

// But what do you do when you need to start an asynchronous action, // such as an API call, or a router transition?

// Meet thunks. // A thunk in this context is a function that can be dispatched to perform async // activity and can dispatch actions and read state. // This is an action creator that returns a thunk: function makeASandwichWithSecretSauce(forPerson) { // We can invert control here by returning a function - the "thunk". // When this function is passed to dispatch, the thunk middleware will intercept it, // and call it with dispatch and getState as arguments. // This gives the thunk function the ability to run some logic, and still interact with the store. return function(dispatch) { return fetchSecretSauce().then( (sauce) => dispatch(makeASandwich(forPerson, sauce)), (error) => dispatch(apologize('The Sandwich Shop', forPerson, error)), ); }; }

// Thunk middleware lets me dispatch thunk async actions // as if they were actions!


// It even takes care to return the thunk’s return value // from the dispatch, so I can chain Promises as long as I return them.

store.dispatch(makeASandwichWithSecretSauce('My partner')).then(() => { console.log('Done!'); });

// In fact I can write action creators that dispatch // actions and async actions from other action creators, // and I can build my control flow with Promises.

function makeSandwichesForEverybody() { return function(dispatch, getState) { if (!getState().sandwiches.isShopOpen) { // You don’t have to return Promises, but it’s a handy convention // so the caller can always call .then() on async dispatch result.

  return Promise.resolve();

// We can dispatch both plain object actions and other thunks,
// which lets us compose the asynchronous actions in a single flow.

return dispatch(makeASandwichWithSecretSauce('My Grandma'))
  .then(() =>
      dispatch(makeASandwichWithSecretSauce('My wife')),
  .then(() => dispatch(makeASandwichWithSecretSauce('Our kids')))
  .then(() =>
      getState().myMoney > 42
        ? withdrawMoney(42)
        : apologize('Me', 'The Sandwich Shop'),

}; }

// This is very useful for server side rendering, because I can wait // until data is available, then synchronously render the app.

store .dispatch(makeSandwichesForEverybody()) .then(() => response.send(ReactDOMServer.renderToString()), );

// I can also dispatch a thunk async action from a component // any time its props change to load the missing data.

import { connect } from 'react-redux'; import { Component } from 'react';

class SandwichShop extends Component { componentDidMount() { this.props.dispatch(makeASandwichWithSecretSauce(this.props.forPerson)); }

componentDidUpdate(prevProps) { if (prevProps.forPerson !== this.props.forPerson) { this.props.dispatch(makeASandwichWithSecretSauce(this.props.forPerson)); } }

render() { return


; } }

export default connect((state) => ({ sandwiches: state.sandwiches, }))(SandwichShop);

Injecting a Custom Argument

Since 2.1.0, Redux Thunk supports injecting a custom argument using the

const store = createStore(

// later function fetchUser(id) { return (dispatch, getState, api) => { // you can use api here }; }

To pass multiple things, just wrap them in a single object. Using ES2015 shorthand property names can make this more concise.

const api = "";
const whatever = 42;

const store = createStore( reducer, applyMiddleware(thunk.withExtraArgument({ api, whatever })), );

// later function fetchUser(id) { return (dispatch, getState, { api, whatever }) => { // you can use api and something else here }; }



We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.