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

oklahoma

v3.1.0

Published

Minimal promise-based finite state manager

Downloads

7

Readme

oklahoma Build Status

Minimal promise-based finite state manager

Install

$ npm install --save oklahoma

Usage

var Oklahoma = require('oklahoma')

var fsm = Oklahoma({
  initial: 'alpha',
  states: {
    alpha: {
      leave: [
        action1,
        action2
      ]
    },
    beta: {
      enter: [
        action3,
        action4
      ],
      entered: [
        callMeAfterEnterIsDone
      ]
    }
  }
})

// Will change the state from 'alpha' to 'beta', running alpha's leave functions in order,
// then beta's enter functions in order.
// If any enter/leave function throws an error or rejects a promise, the state transition will abort.
fsm.go('beta')

API

Oklahoma(options) -> fsm

options
options.initial

Required Type: string

The id of the fsm's initial state.

options.states

Required Type: object

An object where the keys are the ids of available states, and the values are an object describing each state:

  • enter: function|Array<function> - Function(s) that will be called in order when fsm.go is called to enter this state.
  • entered: function|Array<function> - Function(s) that will be called in order after this state is fully entered.
  • leave: function|Array<function> - Function(s) that will be called in order when fsm.go is called to leave this state.

Any enter or leave callback that returns a rejected promise will abort the current state transition.

fsm.current() -> string

Returns the id of the current state.

fsm.done() -> Promise

Returns a promise that will resolve once the fsm is done changing states.

fsm.go(state, [...args]) -> Promise

Transition to the given state id. The id must be a valid target of the current state.

args will be passed into each enter/leave function.

Returns a promise that will be resolved or rejected when this state transition finishes.

If multiple state transitions are queued up at once, they will be run in order.

For example, fsm.go('bar'); fsm.go('baz'); will attempt to transition to bar, then once that completes (success or failure), will attempt a transition to baz.

License

MIT © Andrew Joslin