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

stream-batches

v1.2.0

Published

Yet another stream batching transformation

Downloads

10

Readme

stream-batches

This is an object-mode stream that collects chunks and flushes them as batches.

Flushing happens either when the incoming stream is done, or when a limit is reached.

There are three kinds of limits: bytes, items and time. More than one limit can be active, and a flush occurs when any of them are hit.

Example

Send batches of 10 items through - this is the default behavior.

mySource
  .pipe(batches({ limit: { items: 10 } }))
  .pipe(myDestination)

Collect (up to) 1 MB worth of records:

mySource
  .pipe(batches({ limit: { bytes: 1 * 1024 * 1024 } }))
  .pipe(myDestination)

Collect up to 100 records no larger than 256kb but don't wait longer than 500ms

mySource
  .pipe(batches({ limit: { items: 100, bytes: 256 * 1024, time: 500 } }))
  .pipe(myDestination)

Byte Count

When using a byte limit, the default counter is Buffer.byteLength. This can be customized with a byteCount function passed in via options.

This inflates the byte count by 2 for each record:

mySource
  .pipe(batches({ limit: { bytes: 256 }, byteCount: r => Buffer.byteLength(r) + 2 }))
  .pipe(myDestination)

This might be useful if you're sending a request that has a payload limit, and you want to factor in the overhead of JSON.stringify on the batched array.