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 🙏

© 2025 – Pkg Stats / Ryan Hefner

progress-pipeline

v1.4.0

Published

execute async functions in sequence and get events about their progress

Readme

progress-pipeline

Like async.series, but with a readable-stream interface for getting progress events.

Installation

npm install progress-pipeline

Usage

var series = require('progress-pipeline');

var jobs =[
    function cloning(cb) {
        gitClone(user + '/' + repo, function(err) {
            cb(err, 'done cloning');
        });
    },
    function installing(cb) {
        shell('cd '+ repo +' && npm install', function(err) {
            cb(err, 'done installing');
        });
    }
];

series(jobs).on('data', function(data) {
    console.log(data.jobFinished ? data.result : data.jobIndex + '/' + data.totalJobs + data.job.name + ' ...');
});

output:

0/2 cloning ...
done cloning
1/2 installing ...
done installing

Job Functions

Jobs are regular, node-style async functions, e.g. they are being called with an error-first callback and are required to call that callback with an error and an optional result argument.

Note You can add properties to the job functions before putting them into the pipeline and you will have access to these prperties in your on('data') event handler. See demo.js for an example.

Events

You get two data events per job

  • one when the job has started
{
    jobFinished: false,
    job: <the job-function you provided>
    jobIndex: <zero-based index of this job>
    totalJobs: <total number of jobs in the pipeline>
}
  • and one when the job has finished
{
    jobFinished: true,
    job: <the job-function you provided>
    jobIndex: <zero-based index of this job>
    totalJobs: <total number of jobs in the pipeline>
    result: <the job's result>
}

In case a job fails, the stream emits an error event. The emitted error has the following additional properties:

{
    job: <the job-function you provided>
    jobIndex: <zero-based index of this job>
    totalJobs: <total number of jobs in the pipeline>
}