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

async-fsm

v1.0.3

Published

an abstract finite state machine thing

Downloads

1

Readme

Async FSM

an async style finite state machine.

#How do I use this thing?

you pass it a state table, and it gives you back a function to kick off your state machine

var asfm = require("async-fsm");

var fsm = asfm({
	"start":function(your,args,here,next){
		//do some stuff
		next(null,"phase1",)
	},
	"phase1":function(something,else,next){
		//do what you need here
	},
	"phase2":function(whatever,you,want,next){
		//do some more stuff
		try{
			risky_biz();
		}
		catch(err){
			//we had an error, end things here
			next(err,null,final,args)
		}

		//end here!
		next(null,null,stuff,to,pass,to,the,end);
	}
});

//give it the first state
fsm("start",the,first,args,function(err,args,they,passed,to,the,end){
	//do whatever you want here!
});

each method passes the values after the error and the new state, right now states are only strings, if you pass a non-string into the function it will interpret that as a request to finish the machine and call the end function.

#What about exceptions EXCEPTIONS ARE NOT SAFE

This is a pure async api, and as such it makes no effort to trap or handle excpetions. If one of your functions throws the whole operation will simply blow up and not continue.

unfortunately I can't make any default way that will handle exceptions, because there is always the possiblity that an exception will be thrown after the next function is called.