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

wait-for-stream

v0.0.0

Published

Wait for some data to become available on a stream

Downloads

4

Readme

wait-for-stream

npm install wait-for-stream

A small utility to get exactly the amount of data you need from a stream. Instead of repeatedly calling read until the amount of data you wanted shows up, this does the waiting for you.

methods

new Waiter(stream)

Creates a new Waiter on a stream.

wait.getBytes(length, cb)

Waits until length bytes are available on the stream, and calls cb with those bytes.

wait.getLength(lengthBytes, cb)

Helper function which gets lengthBytes bytes and uses them as a big-endian, unsigned length to get some data. For example, if a TCP stream sends a 32 bit length followed by data of that length, wait.getLength(4, ...) will get the data for you. Valid values for lengthBytes are 1, 2, and 4. I decided to leave out 64 bit lengths as the loss of precision when converting to a JS number may result in intermittant errors. Plus, if you're waiting for more than 4GB of data on a stream, you should probably be using some other method...

examples

var Waiter = require('wait-for-stream');

var stream = net.connect(); // or something
var wait = new Waiter(stream);

wait.getBytes(12, function(data) {
    console.log(data); // Twelve bytes from the stream
});

wait.getLength(2, function(data) { // Get a 2 byte length
    console.log(data); // 55 bytes of stuff
});

Notes

Calling the methods repeatedly without waiting for earlier callbacks to return is perfectly safe. Just remember that the callbacks will get their data in the order the original calls were made.