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 🙏

© 2026 – Pkg Stats / Ryan Hefner

redux-request-generator

v1.0.0-rc.1

Published

Boilerplate-free http requests for redux apps

Readme

redux-request-generator

This is not yet released. API or the way it integrates into redux might change. Feedback welcome.

One function that creates actions and reducers for your http requests.

How is it different?

  • not a middleware
  • has tests

Browser support

By default fetch is used, so it has to be there (or shimmed)

If you're considering shimming fetch, use require('redux-request-generator/xhr') instead. It uses xhr for making http requests.

No support for IE8 or IE9, but you should be able to get it to work.

Usage

const defineRequests = require('redux-request-generator')
const {actions, reducers} = defineRequests(definitions, defaults)

//use in your app
combineReducers({
    ...reducers
});

definitions is a map from state keys to request definitions:

definition:= {
    requestGenerator: (args) => (url or Request object),
    condition: (state) => (boolean), //optional
    mapper: (data) => (data) //optional
}

redux-thunk middleware is required for actions creator to work

Example

  1. Define requests available to your app.
const {actions, reducers} = defineRequests({
    books: {
        requestGenerator: (author) => (`/api/books/by/${author}`),
        mapper: (data, author) => ({[author]: data.results})
    }
}, defaults)
  1. Add thunk middleware and combine defined reducers with your other reducers.
const createStoreWithMiddleware = applyMiddleware([thunk])(createStore)
const reducer = combineReducers({
    myField: myCustomReducer,
    ...reducers
})
const store = createStoreWithMiddleware(reducer)
  1. To fetch data dispatch just one action and both your helper functions will be given the arguments passed to the action.
store.dispatch(actions.books("JRRTolkien"))
  1. Use the key (books) in a component. Show loading indicator while isFetching is true. state.books will contain:
  • isFetching - set to true while the request is waiting for response
  • error - error object if there was an error fetching data {statusCode, messages}
  • data - response or whatever mapper returned after the response came in. Must be an object