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

autoreducer

v0.1.0

Published

useAutoReducer hook around useReducer

Downloads

253

Readme

useAutoReducer

Build Status

useAutoReducer is a React Hook around useReducer that aims to simplify and streamline the usage of complex state in functional React components. Its primary design goal is simplicity and predictability.

Example


import { useAutoReducer } from 'autoreducer';

function MyComponent() {
    const [ state, dispatch ] = useAutoReducer({
        topCount: 0,
        bottomCount: 0 
    }, {
        incrementTop: (prevState) => () => {
            return { topCount: prevState.topCount + 1 };
        },
        incrementBottom: (prevState) => () => {
            return { bottomCount: prevState.bottomCount + 1 };
        },
        incrementBoth: (prevState) => () => {
            return { bottomCount: prevState.bottomCount + 1, topCount: prevState.topCount + 1 };
        }       
    });

    return <div>
        <a onClick={dispatch.incrementTop}>Top: {state.topCount}</a>
        <a onClick={dispatch.incrementBottom}>Top: {state.bottomCount}</a>
        <a onClick={dispatch.incrementBoth}>Increment both</a>
    </div>
}

Usage

useAutoReducer expects two arguments: a state object and an optional set of custom action creators to be added to the dispatcher, and returns an array of [state, dispatcher].

The state object can be whatever you want it to be. Keys from the state object will get parsed and automatically added to the dispatcher as a single-value updater. For example, if you passed a state object of {foo: 1}, dispatch.foo(newFoo: number) gets added to the dispatcher. As a result, custom actions cannot share the same name as state keys.

Custom actions are also automatically added to the dispatcher with the keys you provide. Action creators are functions that take the previous state and return an action (a function that returns a partial state update). Or, more simply, they take the format: (prevState: State) => (...args: any[]) => Partial<State>. The action creators can only accept 0 or 1 (prevState) argument. Actions themselves can take arguments and they will need to be called with those arguments when they're called from the dispatcher.

Check out the tests for more examples!

TypeScript

autoreducer ships with TS definitions, so it should Just Work out of the box! useAutoReducer is type safe, supports dispatcher autocompletion, and should infer your types from the shape of the provided initial state and action creators.

Comparisons with useReducer

Counter

This counter example is sourced from the React useReducer documentation

useReducer

const initialState = {count: 0};

function reducer(state, action) {
  switch (action.type) {
    case 'increment':
      return {count: state.count + 1};
    case 'decrement':
      return {count: state.count - 1};
    default:
      throw new Error();
  }
}

function Counter() {
  const [state, dispatch] = useReducer(reducer, initialState);
  return (
    <>
      Count: {state.count}
      <button onClick={() => dispatch({type: 'increment'})}>+</button>
      <button onClick={() => dispatch({type: 'decrement'})}>-</button>
    </>
  );
}

useAutoReducer


const initialState = { count: 0 };
const actions = {
  increment: state => () => {count: state.count + 1},
  decrement: state => () => {count: state.count - 1}
};

function Counter() {
  const [state, dispatch] = useAutoReducer(initialState, actions);
  return (
    <>
      Count: {state.count}
      <button onClick={dispatch.increment}>+</button>
      <button onClick={dispatch.decrement}>-</button>
    </>
  );
}