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

next-redux-replay

v1.2.1

Published

Use Redux with Next.js

Readme

Next Redux Replay

Use Redux and friends with Next.js.

WARNING: This library only supports Next.js v3. It does not work with later versions.

Differs from next-redux-wrapper in how state is transferred to the client. In next-redux-wrapper, the whole state is sent and used as the preloaded state in createStore(). With Next Redux Replay only the actions responsible for the state are sent, which are then replayed on the client.

Installation

yarn install next-redux-replay

Usage

// some-page.js

import withRedux from "next-redux-replay";

const SomePage = () => <div />;

const makeStore = (actions, nextReduxReplayMiddleware, _isServer) => {
  const store = createStore(
    rootReducer,
    applyMiddleware(nextReduxReplayMiddleware)
  );
  actions.forEach(action => store.dispatch(action));
  return store;
};

const initStore = ({ store, isServer }) => {
  store.dispatch(someAction());
  const initialProps = {};
  return Promise.resolve(initialProps);
}

export default withRedux(makeStore, initStore)(SomePage)

makeStore()

This function should create the store with the provided middleware then replay the recorded actions on the store. The middleware is responsible for collecting actions to be replayed on the client, so it should be placed in the middleware chain accordingly; i.e. after Redux Thunk.

initStore()

Perform any setup and data fetching required here and return a promise. Whatever the promise resolves to will be merged with the wrapped page component's props. This function serves the same purpose as getInitialProps(), but receives the store in addition to the normal `context' object.


Unlike next-redux-wrapper, this library does not connect your page components to the Redux store.