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

flux-hooks

v1.1.4

Published

Hooks implementation for Facebook Flux Util's Stores

Readme

flux-hooks

Hooks implementation for Facebook Flux Util's Stores.

This takes advantage of the new React Hooks API, and is a great alternative to using Flux-Util's Container.

This is an implementation using a combination of useEffect & useReducer and lodash.isequal.

Install

npm add flux-hooks or yarn add flux-hooks

API

const value_from_store = (prevState, store) => {...}

const value = useFluxStore(store: <FluxStore>, value_from_store: Function, deps?: Array, strictEquality?: boolean)

Usage

Basic Usage

Using the CounterStore example from Flux Utils.

import useFluxStore from 'flux-hooks';

const CounterComponent = () => {
  const counter = useFluxStore(CounterStore, (prevState, store) => store.getState())

  return <CounterUI counter={counter} />;
}

Dependencies - deps

The deps parameter is an Array of values as used by useCallback/useMemo.

In cases where the reducer is using other State/Prop, pass them as deps. Normally useReducer would not trigger a dispatch in this case.

import useFluxStore from 'flux-hooks';

const SearchComponent = () => {
  const [query, setQuery] = useState("")

  const results = useFluxStore(SearchStore, (prevState, store) => store.getSearchResults(query), [query])

  return <div>
    <input type="text" value={query} onChange={e => setQuery(e.target.value)} />
    <ul>
      results.map(r => <li>{r}</li>)
  </ul>
  </div>
}

Strict Equality

Default: OFF

Stores can update frequently with our reducer selecting only a small subset of the values. In the cases if you apply a filter on an Immutable-js objects, or return multiple values using an Object, this will cause the Object.is equality check to fail. This defeats the purpose of using the reducer!

To prevent this, lodash.isequal is used by default. This does a deep check whenever the reducer is run, to make sure nothing has changed.

The assumption here is that the equality check is cheaper to run than a re-render.

To opt out of using the more expensive lodash.isequal check set strictEquality (4th argument) to true. This will return to useReducer's default behaviour.