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

oilspill

v2.1.3

Published

Monitors the status of a stream pipeline

Downloads

8

Readme

oilspill

oilspill monitors many streams which have been piped together, allowing you to visualize the overall status of your pipeline. It shows you how much data is currently buffered in each stream's readable and/or writable buffer.

oilspill screenshot

A stream with large amounts of data sitting in its read buffer indicates that the stream is slow to process data relative to the other streams in your pipeline.

This is highly useful to identify where you have bottlenecks.

Example

var Oilspill = require('oilspill');

// now do something with streams, like...
var read = fs.createReadStream(process.argv[2]);
read.pipe(zlib.createGzip()).pipe(fs.createWriteStream('./out.gz'));

// now set up the monitor by passing in the FIRST stream in the pipeline
var monitor = new Oilspill(read, {
    name: 'Gzip Test'
});
os.start();

Now when your app is running, start the monitor client. If you've installed oilspill globally (npm install -g oilspill):

$ oilspill

API

Oilspill(pipeline, options)

Creates a new monitor server instance. pipeline can be the first stream of a pipeline or an array of streams. Options:

  • name: The name of the pipeline (displayed top left in the monitor client)
  • frequency: How often to update the display. Defaults to 250ms.

Oilspill#add(stream)

Adds a single stream to the list of monitored streams

Oilspill#addStreams(pipeline)

Adds a pipeline of streams.

Oilspill#addBreak(label)

Adds a break to the list (appears as a line with ------ and the label)

Oilspill#update()

Immediately updates the display. (This is automatically called every opts.frequency ms.)

Oilspill#start(port)

Starts monitoring the streams and opens the server on the specified port (default 6457).

Oilspill#stop()

Stops monitoring and closes the server.

Oilspill#done(count)

Update the number of processed things. If no count is specified, an internal counter is incremented.

Monitor client

Usage: oilspill

Options:
  -p, --port  Connect to this port                               [default: 6457]

  -h, --host  Connect to this host                        [default: "127.0.0.1"]

  --help      Show help                                                [boolean]