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

stateful-event

v1.0.4

Published

a tiny stateful eventbus in few lines of js

Downloads

10

Readme

a tiny stateful eventbus in few lines of js

Build Status

Usage

var se = require('stateful-event')

var bus   = new se()
bus.debug = true                                      // will output publish() calls in console

var x = bus.subscribe("someprocess/start", function(data, state){
  if( state == "offline" ) return
  // do stuff 
})

bus.subscribe("state", function(state){
  if( state == "online"  ) console.log("fooooo!")
  if( state == "cleanup" ) bus.unsubscribe(x)
})

bus.state("online")                                   // sets state to online 
bus.publish("someprocess/start",{foo:"bar"})          // will fire doFoo()
bus.state("offline")                                  // set state to online
bus.publish("someprocess/start",{foo:"bar"})          // won't fire doFoo
bus.publish("someprocess/start",{foo:"bar"},"online") // set state to "online", and will fire doFoo
bus.publish("someprocess/start",{foo:"bar"})          // will fire doFoo()
console.log( bus.state() )                            // will return "online"
bus.state("cleanup")                                  // will trigger bus.unsubscribe(x)

user login state management:

var bus   = new se({defaultstate:"loggedout"})

function sessionExpired() {
  bus.state( bus.opts.defaultstate = "loggedout" )
}

login( user, pw, sessionExpired, function(){
  bus.state( busopts.defaultstate = "loggedin" )
})

hint: for (arguably) more pretty code, you could use string-variables named like ONLINE instead of "online"

Features

  • event listening and triggering
  • be able to unsubscribe or ignore events in certain state
  • easier to use / extendable compared to EventEmitter
  • maintain state in bus instead of global scope

Functions

bus.state(state)                  // set/get state: state("mystate") or state() returns current state-string
bus.publish(channel, data, state) // publish: publish('some/channel', ['Denis', 'Ciccale'], "mystate" // optional )
bus.subscribe(channel, handler)   // usage: var handle = subscribe('some/channel', function (name, lastName) {})
bus.unsubscribe(handle)           // usage: unsubscribe(handle);