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

prefix-drip-stream

v0.0.3

Published

Given a prefix, this read/write stream will pre-emptively write small increments ("drip") until actual content is written to the stream.

Readme

What

Given a prefix, this read/write stream will pre-emptively write small increments ("drip") until actual content is written to the stream.

Why

The primary use case is to get around things like Heroku's connection timeout (which will die if no data is transferred for 30 seconds). If you have an image manipulation service with a known header, you can write bits of it out in order to buy yourself time.

Example

var request = require('request');
var PrefixDripStream = require('prefix-drip-stream');
var PNG_HEADER = new Buffer('89504e470d0a1a0a', 'hex'); // png's "magic number"
var IMAGE_URL = 'http://upload.wikimedia.org/wikipedia/en/1/13/S3_Graphics_Logo.png';
// pre-emptivly write a bit of the png header every second until we get actual data
var drip = new PrefixDripStream(PNG_HEADER, 1000);

app.get('/', function (req, res) {
  request(IMAGE_URL).pipe(drip).pipe(res);
});

Warnings

  • If you're using this to get around heroku's 30s timeout, you should probably follow their advice and move the processing into a background task...The only reason I went this route is it saved having to use a database entirely.
  • Be certain that you know that the prefix you specify is the first data that will be written to your pipe...otherwise you've just corrupted your data.