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

async-reconciler

v1.0.1

Published

Transition between current and next state with a provided reconciliation function

Downloads

6

Readme

async-reconciler

Reconciles from one state to another, using a reconcile function that you pass. Ignores unnecessary state changes while reconciler is running.

An example use-case for this is where you have some UI to connect/disconnect something, and connection/disconnection takes time, and you shouldn't try to disconnect until you've connected.

import {makeAsyncReconciler} from "async-reconciler"
const {connect, disconnect} = myApi

const reconciler = makeAsyncReconciler({
  initialState: {
    connected: false,
  },
  statesAreEqual(a, b) {
    return a.connected === b.connected
  },
  reconcile(previous, next) {
    if (next.connected && !previous.connected) {
      return connect().then(() => ({
        connected: true,
      }))
    }

    if (!next.connected && previous.connected) {
      return disconnect().then(() => ({
        connected: false,
      }))
    }

    // should not be reached - but we didn't do anything so return old state
    return previous
  },
})

// now quickly switch the connection on and off
reconciler.requestState({connected: true}) // causes connect() to be called

// these are all 'queued' but not executed yes as connect is still happening
reconciler.requestState({connected: false})
reconciler.requestState({connected: true})
reconciler.requestState({connected: false})
reconciler.requestState({connected: true})
reconciler.requestState({connected: false})

// now connect() resolves

// disconnect() is called now, as our final call above, wants our state to be
// disconnected