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

stairs

v0.3.2

Published

Organize your application's steps into stairs.

Downloads

8

Readme

Build Status NPM version David DM

Organize your application's steps with stairs.

Here we are building an extraction process to extract data from some API.

var stairs = require('stairs');

var extractData = stairs('extract data')
  .step('query api', function ($, next) {
    http.get($.url, function (res) {
      $.body = '';
      res.on('data', function (chunk) { $.body = $.body + chunk; });
      res.on('end', next);
      res.on('error', next);
    });
  })
  .step('parse json', function ($) {
    try { $.data = JSON.parse($.body); } 
    catch(e) { return next(e) };
    finally { this.skip('skip to') }
  })
  .step('skip to', function ($, next) {
    this.next();
  })
  .step('grab element', function ($, next) {
    $.extracted = $.data.some.field;
    this.end();
  })
  .on('step', function (title, index, count) {
    console.log('on step "%s" which is %s/%s of process "%s"', title, index, count, this.title);
  });
  .on('error', function (err, $) { 
    console.error(err);
  }) 
  .on('done', function (err, $) {
    console.log('extracted %j', $.extracted);
  });

Next we apply our process to a list of urls.

var urls = [
  'http://some.api?id=1'
  'http://some.api?id=2'
  'http://some.api?id=2'
].forEach(function (url) {
  extractData({url: url});
});

Features

  • Lean
  • Simple
  • Fast
  • Easy

API

Stairs

var stairs = require('stairs');

Stairs#()

Creates a new instance.

var s = stairs();

Stairs#(title:String)

Creats a new instance with a title.

var s = stairs('extraction process');

Stairs#()

Executes the steps in the order in which they were added.

s();

Stairs#(cb:Function)

Executes the steps in the order in which they were added, and when done invokes the callback cb.

s(function ($) {
  console.log($);
});

Stairs#(scope:Object, cb:Function)

Executes the steps in the order in which they were added given a scope and when done invokes the callback cb.

s({}, function ($) {
  console.log($);
});

Stairs#run(scope:Object)

Executes the steps in the order in which they were added given a scope.

s.run({});

Stairs#run(cb:Function)

Executes the steps in the order in which they were added, and when done invokes the callback cb.

s.run(function (err, $) {
  console.log($);
});

Stairs#run(scope:Object, cb:Function)

Executes the steps in the order in which they were added given a scope and when done invokes the callback cb.

s.run({}, function (err, $) {
  console.log($);
});

Stairs#step(title:String, fn:Function)

Adds a step. The step function fn when invoked will get all the parameters in the scope. For most application you may only use one. The last argument will be the next function that will invoke the next step. You may pass an Error object when calling next in order to stop the flow of execution and handle the error.

s.step('query api', function ($, next) {
  http.get($.url, function (res) {
    $.body = '';
    res.on('data', function (chunk) { $.body = $.body + chunk; });
    res.on('end', next);
    res.on('error', next);
  });
});

Stairs#step(title:String, exclude:Boolean, fn:Function)

Conditionally adds a step.

s.step('query api', options.skipQuery, function ($, next) {
  http.get($.url, function (res) {
    $.body = '';
    res.on('data', function (chunk) { $.body = $.body + chunk; });
    res.on('end', next);
    res.on('error', next);
  });
});

The "query api" step will not be added if options.skipQuery is true.

Stairs.Context#skip(title:String)

You can skip to a particular step given the title of that step by calling this.skip('skip to').

s.step('parse json', function ($, next) {
  try { $.data = JSON.parse($.body); } 
  catch(e) { return next(e) };
  finally { this.skip('skip to') }
});

Stairs.Context#next()

You can invoke next from the callback parameter next or this.next().

s.step('skip to', function ($, next) {
  this.next();
});

Stairs.Context#end()

You can end the process by calling this.end() in your handler.

s.step('grab element', function ($, next) {
  console.log('the data %j', $.data);
  $.extracted = $.data.some.field;
  this.end();
});

Events

step

The step event is triggered for each step when being executed.

s.on('step', function (title, i, count) {
  console.log('we are processing step "%s" which is step %s of %s', title, i, count);
});

done

The done event is triggered when the process is complete.

s.on('done', function ($) {
  console.log('done.');
});

error

The error event is triggered whenever we receive an error.

s.on('error', function (err, $) {
  console.error(err);
});

Installation and Environment Setup

Install node.js (See download and install instructions here: http://nodejs.org/).

Clone this repository

> git clone [email protected]:turbonetix/stairs.git

cd into the directory and install the dependencies

> cd stairs
> npm install && npm shrinkwrap --dev

Running Tests

Install coffee-script

> npm install coffee-script -g

Tests are run using grunt. You must first globally install the grunt-cli with npm.

> sudo npm install -g grunt-cli

Unit Tests

To run the tests, just run grunt

> grunt spec

TODO