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

evented-stack

v0.1.3

Published

Evented, Array styled, queue for node

Downloads

13

Readme

evented stack

Evented, Array styled, stack for node

npm install evented-stack

Why

Wanted an Array like queue with juicy behaviour and custom flow control.

Inspired by creationix's stack and jessetane's queue

General idea

On mind:

Get an Array subClass out of the module after which one can add flow control.

  • See ./lib/ArraySubClass.js or the awesome kangax post on how to do that.

Have the thing inherit from EventEmitter so one can plug flow control on the known array methods.

Niceness:

  • One should be able to switch the events on and off.
  • set and get methods to store simple data between layers of the stack.

Defaults:

  • For iterative methods such as forEach, events are emitted. See below example for more information on this.

Note: right you can push everything to the stack. In the future that might change.

Usage

As an example, lets make a middleware that will measure the time of a request.

var http = require('http');
var Stack = require('evented-stack'); // Array subClass - EventEmitter
var stack = new Stack();

// Elements of the stack
stack.push(function stackFn1(req, res){

    stack.set('request time', new Date())
    res.write('There is no dark side of the Moon.')

    return 'Layer 1!';

  }).push(function stackFn2(req, res){

    res.write('\nAs a matter of fact ')
    return 'Layer 2!';

  })

// Events
stack.once('start', function onStart(req, res){ // Once call back

    console.log('onStart: Next time I won\'t be here')

  }).on('next', function onNext(req, res){

    console.log('onNext: In between layers of the stack')

  }).on('end', function onEnd(req, res){

    console.log('onEnd: finished!')
    var time = ( new Date() - stack.get('request time') ).toString();

    res.write('it\'s all dark.');
    res.write('\n\n');
    res.end('The request took ' + time + ' ms');
  })

At this point the stack is

console.log(stack)
 [ [Function: stackFn1],
  [Function: stackFn2] ]
console.log(stack._events)
 { start: { [Function: g] listener: [Function: onStart] },
    next: [Function: onNext],
     end: [Function: onEnd] }

Now we can hook it up to a http.Server

var Server = http.createServer(function(req, res){

  // We can choose to keep events quiet
    stack.silent = true;
  // Or listen on demand
    stack.silent = false;

  // We could use stack.forEach but we'll use the build-in method #run
  // is like [].forEach but fires 3 events: `start`, `next` and `end`
  // spec: stack.run(stackArgs [,callback(lasRet, index, allReturns)])
  stack.run(req, res, function(lastReturn, index, returns){
    console.log('\nstack[' + index-1 + '] returned ', lastReturn, '\n');
  })
})

Server.listen(3000, function(){
  console.log('Server running on port '+3000);
})

API

At this point the package is still on flux. Right know you can expect, Array and EventEmitter like api.

If you are curious look at ./lib/Stack.js. In any case this might change

License

MIT