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

@div-int/typedfsm

v0.0.5

Published

A TypeScript finite state machine library

Downloads

8

Readme

typedfsm

CircleCI Codacy Badge Codacy Badge

A TypeScript Finite State Machine library.

Example

First create an enum with the states and possible actions on those states. It can have text values:

const enum GhostStates {
  Waiting = 'Waiting',
  Chasing = 'Chasing',
  Scatter = 'Scatter',
  Frightened = 'Frightened',
  Eaten = 'Eaten',
  Paused = 'Paused',
}

const enum GhostActions {
  Wait = 'Wait',
  Chase = 'Chase',
  Scatter = 'Scatter',
  Frighten = 'Frighten',
  Eat = 'Eat',
  Pause = 'Pause',
}

or just a plain numeric enum:

const enum GhostStates {
  Waiting,
  Chasing,
  Scatter,
  Frightened,
  Eaten,
  Paused,
}

const enum GhostActions {
  Wait,
  Chase,
  Scatter,
  Frighten,
  Eat,
  Pause,
}

To create the typed finite state machine use the following code with the previously defined enum and the start/default state of the machine as a parameter.

const ghostState = new Typed.FSM<GhostStates>(GhostStates.Waiting);

To create states/transitions we first call the from() method on the ghostState object, this will create a state of Waiting. To add a transition rule to this state we can chain the to() method to this call and give it the state Chasing. This will allow us to go from Waiting to Chasing but not from Chasing to Waiting. Next we call the toFrom() method which will create a transition rule to allow us to change from Waiting to Paused and from Paused back to Waiting.

ghostState
  .from(GhostStates.Waiting, GhostActions.Wait)
    .to(GhostStates.Chasing, GhostActions.Chase)
    .to(GhostStates.Scatter, GhostActions.Scatter)
    .toFrom(GhostStates.Paused, GhostActions.Pause);

To change the state of the finite state machine we can either specify the new state to change to:

ghostState.change(GhostStates.Chasing);

Or tell it an action to perform:

ghostState.do(GhostActions.Chase);