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

fisma

v0.6.0

Published

A FInite State MAchine built with iterators

Downloads

2

Readme

FISMA

What is it

Fisma is a 422b (br,min) **fi**nite **s**tate _ma_chine that is built on Generators. It features entry/exit actions, events, sending signals to transition to a specific state.

How to use

import { createMachine } from 'fisma';

const m = createMachine([
    'A',
    { type: 'B' },
    {
        type: 'C',
        // Add enter and exit 
        // action as a method
        // or array of actions
        enter() {},
        exit: [() => {}]
    },
    {
        type: 'D',
        on: {
            RESTART: 'A'
        }
    },
    {
        type: 'E',
        on: {
            RESTART: {
                target: 'A',
                actions: [ () => console.log('Running actions') ]
            }
        }
    }
]);

// getters
m.current; // A (The active state)
m.done; // false (is the machine running)

// Use `next` to go to the
// next state in array order
m.next();

m.current; // B

// `.subscribe()` returns a cleanup function
const unsub = m.subscribe((ctx) => console.log(ctx));
m.next(); // { type: 'B' }
m.next(); // { type: 'C' }
unsub();

// Pass a string with the
// name of the desired next state
m.next('A');

m.current; // A

m.next('D');
// Signal to the machine a specific
// state to transition to
m.send('RESTART');

m.current; // A

m.next('E');
m.send('RESTART'); // Running actions

m.destroy(); // kills machine
m.done; // true

Things to be aware of

  • There isn't a .start(initialState) method. The initial state is always the first item in the states array.
  • While actions are passed a "context" object, currently the context is the active state object and it is not safe to store or alter that information.
  • ~~active and done might be confusing, active is for the name of the active state, done is the status of the machine itself.~~ active has been changed to current

To Do

  • [ ] Give a proper "context" object for actions and listeners
  • [ ] Accept a more complex "requested state" in the .next() method
  • [ ] Review method and getter names, e.g. ~~active vs. current~~, next() vs. somethingElse()
  • [ ] Should there be an initial getter
  • [ ] Shave bytes