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 🙏

© 2026 – Pkg Stats / Ryan Hefner

command-stack

v0.1.0

Published

An internal router for managing control flow / application state

Readme

Command Stack

Command Stack is a simple router intended for internal routing of application state (and not for http requests or browser pushState).

The idea is to enforce a familiar route driven, synchronous control flow to your application to ensure consistent handling of state.

Asynchronous functions are accommodated with standard callback pattern and modularity encouraged via middleware.

Install

npm install --save command-stack

Usage

var cs = require('command-stack')

cs.listen('/', function(state, next) {
   //functionality here
   next(null, state)
})

The route definition above itself is middleware, we simply listen for the desired route and call next()

And when you are ready to invoke the route:

cs.fire('/', state, function(err, newState) {
  //any function listening for the given route will do it's thing...
  //each listener function is fired in the order it was defined.
  //the callback from fire receives the final result after all listener functions have completed
  //so if the fire command was called from within
  //another fire event already underway, you can now pass state up to the original stack again.  
})

Because of the guaranteed synchronous execution of the middleware stack you can nest commands that 'go horizontal' from within this stack; without breaking or complicating the overall control flow of the application. Ex:

cs.listen('/action', function(state, next) {
    //Branch off and fire another stack: 
    cs.fire('/another-action', state, function(err, newState) { 
        next(null, newState) //< Return the modified state to original stack.
    })
})

Each fire the state object is modified to include a req property with the corresponding route and parameters. Ex: state.req

Modularity

The current hypothesis is that now you have a super simple control flow to your application you can focus on building actual functionality via modules that stack together as middleware. Modules for your app can simply drop in as a function that runs an cstack.listener or set of cstack.listeners.

TODOs

  • Document more clearly the state.req object
  • Write tests
  • Get catch-all wildcard listeners ie: cstack.listen('*') working as expected