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 🙏

© 2024 – Pkg Stats / Ryan Hefner

redux-substore

v0.2.62

Published

Collected actions, reducer, epic and state for any async operation.

Downloads

15

Readme

redux-substore

Collected actions, reducer, epic and state for any async operation.

Build Status

Install

npm install redux-substore --save

Run the demo!

npm run demo

The demo shows how redux-substore can manage two types of requests: one that succeeds and one that fails.

How to use it:

Setup

Construct a new Substore that will manage the getMyData() request function.

import Substore from 'redux-substore'

export default new Substore({
  prefix: 'MY_PREFIX',
  promiseFunction: args => getMyData(args),
  responseMap: response => response['keyWhereMyDataIs'],
})

The prefix will be used to label the action types for this substore. The function passed to promiseFunction: must return a promise that will resolve with the response or reject with an error. Alternatively, send callbackFunction: with a Node-style callback with signature function(err, data). The responseMap: function will receive whatever the request function resolves or calls back with, and should use the response to generate the substore's state. responseMap should generate the initialState for the substore when it receives null.

Integrate with Redux

Add the reducer and epic to your combineReducers and combineEpics:

import { combineReducers } from 'redux'

rootReducer = combineReducers({
	...
	myData: myDataSubstore.reducer
})
import { combineEpics } from 'redux-most'

rootEpic = combineEpics([
	...
	myDataSubstore.epic
])

Manage Your Async Ops

Trigger the request by dispatching the result of requestAction()

store.dispatch(mySubstore.requestAction(requestParams))

Parameters passed to the requestAction will be passed on to the request function supplied as promiseFunction: or callbackFunction: when the Substore was constructed. The action has type MY_PREFIX_REQUEST and when it completes, MY_PREFIX_REQUEST_SUCCESS or MY_PREFIX_REQUEST_FAILURE will be dispatched accordingly.

Access the status and data of the substore by selecting the key you assigned in combineReducers:

getState().myData.isLoading

getState().myData.error

getState().myData.data (default responseMap sets this key)

Clean up

If you need to remove the data in the Substore, dispatch mySubstore.clearAction().