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-reaction-chamber

v1.0.2

Published

A state store for React, optimized for use within Next.js

Readme

reaction-chamber

React state manager

goals

  • Stores instantiated by key. Components on disparate pages can access the same store via key.
  • Automatically wrap components in a store without having to manually convert to props.
  • Merge typical web state storage locations (like URL params) into the state object (Planned).

why not redux/reflux/etc/...?

Redux et al require the app to be constructed a certain way. The primary goal of this project is to reduce the amount of boilerplate needed by anticipating common use cases, while still giving the developer power over their app.

import

Import ReactionChamber with import ReactionChamber from 'next-reaction-chamber'.

api

To wrap your component in a ReactionChamber, create a ReactionChamber component with an id key.

Additionally, if desired, provide an initial state for the store via initialState:

<ReactionChamber id={'my-store-id'} initialState={ /* initial state object, defaults to {} if not passed */ }>
  { /* sub component */ }
</ReactionChamber>

Do note that the id key allows ReactionChambers to be shared across pages by using the same id.

async initial state

The simplest way to handle async initial state is with Next.js-powered getInitialProps.

You can then pass the initial state to your ReactionChamber instance.

static async getInitialProps() {
  return {
    initialState: { myInitialState: 0 }
  }
}

render() {
  return (
    <div>
      <ReactionChamber id={'my-store-id'} initialState={this.props.initialState}>
        { /* sub component */ }
      </ReactionChamber>
    </div>
  )
}

accept ReactionChamber props

ReactionChamber will pass two props to its direct children:

property | description --- | --- store | This is the ReactionChamber state. setStore | This method works very similar to React's own setState, it just sets the state for ReactionChamber.

Example component:

const Demo = ({ setStore, store: { count } }) => {
  return (
    <div>
      <h1>next-reaction-chamber demo component</h1>
      <div>Clicks: {count}</div><br/>
      <button onClick={() => setStore({ count: count + 1 })}>Increment</button>
    </div>
  )
}