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-reactions

v1.3.0

Published

Fire a callback when actions are dispatched

Downloads

7

Readme

redux-reactions

Action handler middleware for Redux.

npm version

npm install --save redux-reactions

Motivation

I felt I needed a way to wait for an action to be dispatched in Redux, and respond to it in some way other than manipulating the store.

Like redux-saga, but much lighter.

Inspiration

Lots of people have had a take on this, here are some middlewares I found that may suit you better:

Usage

First, register the middleware:

store.js

import { createStore, combineReducers, applyMiddleware } from 'redux';
import { createReactionsMiddleware } from 'redux-reactions';
​
const todoApp = combineReducers(reducers);
const store = createStore(
  todoApp,
  applyMiddleware(createReactionsMiddleware())
);

Next up, just like your actions go into a seperate file; for example actions/index.js, your reactions should also be seperated:

reactions/index.js

import * as constants from "./constants";

export function handleNewTodo(addReaction) {
  addReaction(constants.ADD_TODO, (dispatch, getState, action) => {
    /*
       * Do something, but don't dispatch ADD_TODO again or
       * you will enter a loop.
       * 
       * You can perform asynchronous work here.
       */
  });
}

And now in your container, register your reactions:

containers/todo.js

import { connect } from 'react-redux';
import { registerReactions } from 'redux-reactions';

import TodoList from 'components/TodoList';
import * as reactions from './reactions';
​
const mapStateToProps = state => ({});
const mapDispatchToProps = dispatch => ({});

registerReactions(reactions);
​
export default connect(
  mapStateToProps,
  mapDispatchToProps
)(TodoList);

Thanks

Many thanks to Ben Anderson for giving up the redux-reactions npm package name.