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

turnpike-sm

v1.1.0

Published

A small finite state machine for JavaScript

Downloads

3

Readme

Turnpike

A minimal finite-state machine for JavaScript.

Installation

$ npm install turnpike-sm --save

Usage

const Turnpike = require('turnpike');

const turnpike = new Turnpike(initialState, transitions, options);

initialState and transitions are required. The first is the initial state for the state machine to start in, the second is an array of transitions that will happen when a given action (name) occurs;

const turnpike = new Turnpike('asleep', [
  { name: 'bother', from: 'asleep', to: 'awake' },
  { name: 'bother', from: 'awake', to: 'bothered' },
  { name: 'rest', from: 'jumping', to: 'asleep' },
  { name: 'jump', from: Turnpike.ANY, to: 'jumping' }
]);

The special value Turnpike.ANY will match any from state.

The third argument (opts) currently accepts 1 option: opts.EventEmitter is an alternative EventEmitter implementation to use, if your platform doesn't include node's require('events').

instance methods include:

turnpike.act(actionName, [...args])   // Perform an action
turnpike.getState()                   // Retrieve the current state

Turnpike includes an EventEmitter and provides several events on each state transition:

turnpike.on('exit:asleep', (...args) => {
  console.log('Sleep over', args);
});

turnpike.on('exit', (stateName, ...args) => {
  console.log(`Exiting ${stateName} with args:`, args);
});

turnpike.on('enter', (stateName, ...args) => {
  console.log(`Entering ${stateName} with args:`, args);
});

turnpike.on('enter:jumping', (height, speed) => {
  console.log(`Started jumping, height: ${height}, speed: ${speed}`);
});

turnpike.act('jump', 12, 'fast');

Testing / Linting

$ npm test
$ npm run lint

Migrating from 0.x to 1.x

A few minor breaking changes:

  • Initial state is now a separate argument.
  • ev was renamed to name in the event definition.
  • Now uses EventEmitter syntax (on('event', ...)) rather than bespoke onEnter / onExit handlers.
  • No more browser build provided - you should be bundling that yourself.

License

MIT