npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

redux-async-helper

v0.1.5

Published

A tool to help reducing redux code boilerplate for general async usage

Downloads

12

Readme

Redux Async Helper

GitHub GitHub package version npm bundle size (minified + gzip) npm

Opinionated way to reduce boilerplate on async (or sync) logic, like fetching data etc. Zero dependency (Although it only makes sense to use together with Redux AND Redux Thunk).

Installation

npm i redux-async-helper

Usage

See example usage.

Basically, we have these utilities:

  1. createAction
  2. createReducer
  3. createAsyncActions
  4. asyncInitialState
  5. createAsyncHandlers
  6. createAsyncThunk

createAction

This is a simplified version of the one used in redux-act.

const myAction = createAction('my_action');
myAction.toString(); // my_action
myAction(); // { type: 'my_action', payload: null, error: false }
myAction({ my: 'payload' }); // { type: 'my_action', payload: { my: 'payload' }, error: false }
myAction(new Error('error'))); // { type: 'my_action', payload: Error('error'), error: true }

createReducer

This is a helper function to make reducer based on handlers. Basically a handler is a function receiving two arguments, state and payload and returns the modified state.

const myHandlers = {
  [myAction]: state => ({ ...state, count: state.count + 1 })
};

const myInitialState = {
  count: 0
};

const myReducer = createReducer(myHandlers, myInitialState);

createAsyncActions

Used to make a set of actions (request, success, fail, reset) to be used in other async helpers.

asyncInitialState

An opinionated state for holding async state and data. Used with other async helpers.

createAsyncHandlers

Used to make a set of handlers for the async actions generated with createAsyncActions. This function also allows you to hook on each async state with another handlers (onRequest, onSuccess, onFail). Received to arguments, the async actions and hook handlers.

const myFetchingHandlers = createAsyncHandlers(myAsyncActions, {
  onSuccess: state => ({ ...state, progress: 100 })
});

const myHandlers = {
  ...myFetchingHandlers
  // ... other handlers
};

createAsyncThunk

Used to create a thunk (see redux-thunk) for starting (request) the async function. Received three arguments: async actions, the async function, and options, which includes hooks for success (onSuccess) and fail (onFail), each receiving the dispatch and getState as any other thunks. The async function is expected to resolve the data (which will be placed in data key in the state tree produced by initialAsyncState), any errors caught will be placed in the error key.

const apiFetch = async () => {
  try {
    const response = await axios.get('/users');
    return response.data;
  } catch (err) {
    throw err;
  }
};

const fetchThunk = createAsyncThunk(actions, apiFetch, {
  onSuccess: () => console.log('success!')
});