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

sbs

v1.0.0

Published

Sync Buffer Stream: A stream that synchronously buffers and then drains on the next tick.

Downloads

3

Readme

Sync Buffer Stream Build Status

A stream that synchronously buffers and then drains on the next tick. For use when you want to consolidate the chunks that get passed to another stream. Accepts an optional size argument which will trigger a synchronous drain.

var SBS = require('SBS');
var sbs = new SBS(1024);

sbs.on('data', function (d) {
  console.log('chunk is %s bytes long', d.length);
});
sbs.write('foo');
sbs.write('bar');
process.nextTick(function (){
  sbs.write('baz');
});
// chunk is 6 bytes long
// chunk is 3 bytes long

why

take the stream created by this function

function createHmacer(key) {
  return through2.obj(function (chunk, _, next) {
    var out = {data: chunk};
    out.hash = crypto.createHmac('sha512', key).update(chunk).digest();
    next(null, out);
  });
}

it generates an hmac for each chunk it gets and outputs it as an object, as a sha512 hash is 64 bytes this adds a bit of overhead so we'd like to consolidate message as much as possible, but that being said if we get a small standalone message we'd still like that to be sent, i.e. something like.

var stream = new PassThrough();
var i = 0;
while (i++ < 200) {
  stream.write(i.toString());
}
var int = setInterval(function (){
  
    stream.write(i.toString());
  if (++i > 210) {
    clearInterval(int);
  }
}, 1000);

if you pipe that directly to createHmacer it'll compute 210 hmacs, you pipe it through this and it'll compute 11, if you don't want to buffer more then 100 bytes worth of stuff, you can set the max cache to 100 and it'll compute 15 hmacs.

// 210
stream.pipe().pipe(createHmacer('key'));
// 11
stream.pipe(new SyncBufferStream()).pipe(createHmacer('key'));
// 15
stream.pipe(new SyncBufferStream(100)).pipe(createHmacer('key'));