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

jsonstream2-native

v1.0.0

Published

A streaming JSON parser with a streams2 interface

Downloads

11

Readme

JSONStream2-native

This module is based on JSONStream, but uses node's streams2 rather than hacking in something else.

Most importantly, this means that this streaming JSON parser actually respects backpressure when piped.

The input side is a normal Writable stream that takes bytes; the output side is an objectMode Readable.

JSONStream2.parse(path, map, opts)

path and map are the same as JSONStream. There are three opts:

  • encoding - The input (writable) stream's text encoding.
  • writableHighWaterMark - The input (writable) side's highWaterMark in bytes. This is the buffer level when write() starts returning false. Default = 16 kB.
  • readableHighWaterMark - The output (readable) side's highWaterMark in objects. When the readable buffer is full, JSONStream2 will stop parsing incoming bytes until parsed objects are read out. Default = 128

A note on memory usage

Parsed objects can take up significantly more memory than raw bytes sitting in a Buffer. Additionally, you want to avoid buffering in the first place by informing your source (ie the file you've piped in) to pause the deluge of bytes until downstream work is done. Therefore, it is very important that you set an appropriate highWaterMark on any streams that you pipe this in to. In objectMode, node's default of 16,384 applies to the count of objects, not the actual size of the data in those objects.

If you're dealing with objects that are large or contain large strings, you may quickly exhaust your RAM by buffering thousands of objects if one of your downstream streams is slow to consume.