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

state-charts

v2.0.1

Published

State charts implementation.

Downloads

6

Readme

state-charts

Implementation of finite-state automaton and state diagram in TypeScript.

Finite State Machine

Models finite-state machine with conditional transitions.

Configuration

The machine has 3 configuration parameters.

Event Emitter

Object implementing the interface:

interface EventEmitter {
  emit: (name: string, payload: any) => void;
  on: (name: string, cb: (payload: any) => void) => void;
}

It is used to dispatch events on leaving and entering states.

States

Array of state objects.

interface State {
  name: string;
  transitions: Transition[];
}

Transitions are defined as:

interface Transition {
  action: string;               // Action name
  to: string;                   // Target state
  condition?: () => boolean;    // Condition which must be fulfilled to enable transition
}

Initial state

Initial state is not entered until machine.init() method is called. Thanks to that it is possible to subscribe to entering event of the inital state

Events

There are two types of events emitted through the event emitter:

  • FSM.events.enter - emitted on entering a state
  • FSM.events.leave - emitted on leaving a state

Each event is emitted with payload. The payload is the state for which the event happens.

Example

Example of usage:

// Optional, you can use your own event emitter object
import * as EventEmitter from 'eventemitter3';

const eventEmitter = new EventEmitter();
const initialState = {
  name: 'A',
  transitions: [
    {
      action: 'to A',
      to: 'A'
    },
    {
      action: 'to B',
      to: 'B'
    },
  ]
};
const machine = new FSM(
  eventEmitter,
  [
      initialState,
      {
          name: 'B',
          transitions: [
              {
                  action: 'to C',
                  to: 'C',
                  condition: () => false,
              }
          ],
      },
      {
          name: 'C',
          transitions: [],
      }
  ],
  initialState,
);

eventEmitter.on(FSM.events.enter, state => console.log(`Entering state "${state.name}".`));
eventEmitter.on(FSM.events.leave, state => console.log(`Leaving state "${state.name}".`));

machine.init();
// -> Entering state "A".

machine.dispatch('to B');
// -> Leaving state "A".
// -> Entering state "B".

machine.dispatch('to C');
// Nothing happens because condition is not met.

State Charts

Finite-state machines are a great tool to describe automatons. However, it's not an efficient tool to model nested states. This is where state charts come in handy.

Project setup

Run yarn to install project dependencies.

Run yarn test and yarn test:coverage to fire up unit tests. 100% coverage is required. Tests are fired on pre-commit and pre-push hooks with Husky. Open state-charts/coverage/lcov-report/index.html to see coverage report.