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

filepile

v0.0.7

Published

file backed local work queues

Readme

filepile Build Status

file backed work queues

use

var filepile = require('filepile');

// create a new pile called 'emails'
var pile = filepile('emails', function(details, done) {
    // details is whatever job data you provide
    // call done() when done
});

// add things to the pile
// the will be processed by the function above
pile({ to: '[email protected]', body: 'hello' });

multiple producers single consumer

Each filepile will only allow for one consumer but multiple producers. Any named pile which already has a consumer on the same system will not allow another consumer to process jobs. If one of the consumers dies, then another consumer will start.

var cluster = require('cluster');

if (cluster.isMaster) {
    for (var i=0 ; i<4 ; ++i) {
        cluster.fork();
    }
    return;
}

var filepile = require('filepile');

// only one of the processes will invoke this function
var pile = filepile('emails', function(details, done) {
    console.log(details);
    done();
});

// both processes will generate "work"
setInterval(function() {
    pile({ foo: 'bar' });
}, 1000);

how it works

All producers write json files to a folder in /tmp. These files are read by the single consumer and processed. A lockfile is used to ensure that there is only one consumer.

The consumer listens using fs.watch for new files and processes them.

gotchas

filepile is not meant to work across machines at this time and will only ensure one consumer with multiple processes on the same machine.

install

npm install filepile