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

describe-redux

v0.7.1

Published

Substitution for describe function made to test redux actions/reducers in a simple fashion

Readme

npm install describe-redux

describeRedux() is a substitute for regular describe(). Under the hood it creates a redux store and passes an object containing the store, it's state getter and bound actions to the callback.

In the examples the typescript-fsa lib is used to create actions, but it should not make any difference.

It has the following signature:

function describeRedux<S extends {}, A extends ActionCreatorsMapObject>(
  // a test suite description (similar to `describe()`)
  description: string,
  
  // a reducer
  reducer: Reducer<S>,
  
  // an initial state
  initialState: S,
  
  // actions (of type ActionCreatorsMapObject which is an object)
  actions: A,
  
  // callback which received an argument `redux` which allow to access the store
  callback: (redux: DescribeReduxContext<S, A>) => void
): void;

The callback argument has the following type

type DescribeReduxContext<Sextends {}, A extends ActionCreatorsMapObject> = {
  // redux store
  store: Store<S>;
  
  // state getter (same as store.getState())
  state: Readonly<S>;
  
  // bound actions
  actions: A;
};

A full example can be found under the examples folder

import { expect } from 'chai';
import { describeRedux } from 'describe-redux';
import * as actions from './actions';
import { initialState, reducer } from './store';


describe('Test store', () => {

  // with initial state
  describeRedux(
    `action ${actions.addItem.type}`,
    reducer,
    initialState,
    actions,
    redux => {

      it('should add item', () => {
        redux.actions.addItem({id: 'test-id'});
        expect(redux.state.items).to.eql(['test-id']);
      });

  });

});