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

use-history-reducer

v0.1.2

Published

Immer-based reducer with undo/redo, checkpoints, and forking

Downloads

9

Readme

useHistoryReducer

This experimental hook provides a light wrapper over useReducer which provides undo/redo, forking, and checkpoints. It's built on top of Immer, so you also get the added benefits it provides.

Basic example

import React from "react";
import useHistoryReducer from "use-history-reducer";

function reducer(state, action) {
  if (action.type === "increment") {
    state.count += 1;
  }
}

function App() {
  const [state, changes, dispatch] = useHistoryReducer(reducer, { count: 1 });

  return (
    <div>
      <main>{state.count}</main>
      <button onClick={() => dispatch({ type: "increment" })}>++</button>
      <button
        disabled={changes.counts.undos === 0}
        onClick={() => changes.undo()}
      >
        Undo
      </button>
      <button
        disabled={changes.counts.redos === 0}
        onClick={() => changes.redo()}
      >
        Redo
      </button>
    </div>
  );
}

Forking

Forking allows you to break off from the main set of changes temporarily, and either commit all the changes that happen during the fork at once (and in one changeset), or revert them altogether. One use case for this is an input that may change the state many times, and you want only the final value to be recorded.

import React from "react";
import useHistoryReducer from "use-history-reducer";

function reducer(state, action) {
  if (action.type === "SET_COUNT") {
    state.count = action.payload;
  }
}

function App() {
  const [state, changes, dispatch] = useHistoryReducer(reducer, { count: 1 });

  return (
    <div>
      <main>{state.count}</main>
      <input
        type="range"
        min="1"
        max="100"
        value={state.count}
        onMouseDown={() => changes.fork()}
        onMouseUp={() => changes.commit()}
        onChange={e => dispatch({ type: "SET_COUNT", payload: e.target.value })}
      />
      <button
        disabled={changes.counts.undos === 0}
        onClick={() => changes.undo()}
      >
        Undo
      </button>
      <button
        disabled={changes.counts.redos === 0}
        onClick={() => changes.redo()}
      >
        Redo
      </button>
    </div>
  );
}

Checkpoints

By using checkpoints, you can get the the changes made since the last checkpoint. This makes it easy to track unsaved changes you haven't sent to your backend or whatever persistence layer you are using.

import React from "react";
import useHistoryReducer from "use-history-reducer";

function reducer(state, action) {
  if (action.type === "increment") {
    state.count += 1;
  }
}

function App() {
  const [state, changes, dispatch] = useHistoryReducer(reducer, { count: 1 });

  return (
    <div>
      <main>{state.count}</main>
      <button onClick={() => dispatch({ type: "increment" })}>++</button>
      <button
        disabled={changes.counts.unchecked === 0}
        onClick={() => {
          const changes = changes.checkpoint();
          // do something with the patches.
        }}
      >
        Save
      </button>
    </div>
  );
}