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

joes-state-machine

v0.0.6

Published

A simple, easy, and versatile state machine

Readme

Joe's State Machine

A simple, easy, and versatile state machine

const {StateMachine, newState, newTransition}
  = require('joes-state-machine');

let cat = new StateMachine({
  states: [
    newState('sleepy',
      () => console.log('The cat fell asleep'),
      () => console.log('The cat was no longer asleep!')),
    newState('awake',
      () => console.log('The cat woke up!'))
  ],
  transitions: [
    newTransition('sleepy', 'awake',
      () => console.log('The cat transitioned from asleep to awake'))
  ],
  initialState: 'sleepy',
  initialOnEnter: true // Trigger the initial onEntry callback
});

cat.goto('awake');

In this case, if initialOnEnter is true, the first callback passed to the 'sleepy' state will be called when the state machine is constructed. This may not be desired, for example you may want to control when the initial callback is called. initialOnEnter defaults to false.

Another way to call the initial callback is to simply not specify the initial state in the constructor, and then later transition to the desired initial state:


let cat = new StateMachine({
  states: [
    newState('sleepy',
      () => console.log('The cat fell asleep'),
      () => console.log('The cat was no longer asleep!')),
    newState('awake',
      () => console.log('The cat woke up!'))
  ],
  transitions: [
    newTransition('sleepy', 'awake',
      () => console.log('The cat transitioned from asleep to awake'))
  ]
});

cat.goto('sleepy'); // 'The cat fell asleep'...
cat.goto('awake'); // will trigger the other callbacks

There are also shorthands for creating state machines, states, and transitions:

const {newStateMachine, ns, nt} = require('joes-state-machine');

let cat = newStateMachine(
  [
    ns('sleepy',
      () => console.log('The cat fell asleep'),
      () => console.log('The cat was no longer asleep!')),
    ns('awake', () => console.log('The cat woke up!'))
  ],
  [
    nt('sleepy', 'awake',
      () => console.log('The cat transitioned from asleep to awake'))
  ],
  'sleepy',
  true // Trigger the initial onEntry callback for the sleepy state on object construction
);

cat.goto('awake');