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

finitus

v1.2.0

Published

A flexible finite state machine.

Readme

Finitus

A flexible finite state machine.

Travis GitHub release license npm

Installation

Get the distribution package from npm:

npm install finitus

Or source material from git:

git clone https://github.com/jonoco/finitus.git

Useage

Create the machines

Import the finite state machine (FSM) object, Action, and any optional premade actions.

const { FSM, Action, sendEvent } = require("fsm");

Create the state machines.

// Creation order will determine the order of evaluation
const switchSM = FSM.create("Switch");
const handSM = FSM.create("Hand");

Add states to the state machines.

// The first state added to a machine will become the initial state
switchSM.addState('Off');
switchSM.addState('On');
handSM.addState('Flicking');

Link states together.

// Creates unidirectional link: Off -> On
switchSM.linkState('Off', 'On', 'flick on'); 

Create a new Action.

// All Actions must be Async Functions and return true on successful completion
const logMessage = async (msg) => {
    console.log(msg);
    return true;
}

Add actions to the state machine's states.

switchSM.addAction('On', new Action(logMessage, 'light on'));
handSM.addAction('Flicking', new Action(sendEvent, 'flick on'));

Evaluate all state machines.

Evaluating this particular state changes will take a maximum of three evaluation cycles. This can be done by chaining promises together, via an asynchronous loop, or using the built in looping method.

Chaining:

FSM.evaluate()
    .then(() => { 
        console.log('>> first evaluation complete');
        return FSM.evaluate(); 
    }).then(() => { 
        console.log('>> second evaluation complete'); 
        return FSM.evaluate();
    }).then(() => {
        console.log('>> third evaluation complete');
    });

Async loop:

const asyncLoop = async () => {
    for (let i = 0 ; i < 3 ; i++) {
        await FSM.evaluate();
        console.log('evaluation ' + i + ' complete');
    }
}
asyncLoop();

Internal loop:

FSM.evaluate(true); // Will loop continuously in 10 ms cycles.

Expected output.

Using the Promise chaining method:

Switch: evaluating state of machine
Switch: current state is Off
Hand: evaluating state of machine
Hand: current state is Flicking
>> first evaluation complete
Switch: evaluating state of machine
Switch: current state is Off
Switch: received actionable event: flick on
Switch: changing state from Off to On
Hand: evaluating state of machine
Hand: current state is Flicking
>> second evaluation complete
Switch: evaluating state of machine
Switch: current state is On
light on
Hand: evaluating state of machine
Hand: current state is Flicking
>> third evaluation complete

Lifecycle

  • Evaluate ->
  • Check if state has not evaluated or is set to loop ->
    • State machine runs actions on current state ->
  • State machine processes event queue ->
  • Signal the evaluation is complete

License

MIT