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

express-stream-json

v0.0.5

Published

Express middleware for streaming json arrays

Downloads

8

Readme

#express-stream-json

Middleware for express that streams a json array to the response stream.

Express normally serves json by stringifying an object and sending to the response in one chunk. This, of course, means that you have to have the entire object in memory before you can start the response.

This middleware is for the use case where one is using streams server side and don't want to consume that stream and create a huge object in memory on the server. It is especially useful when you are retrieving database records as an object stream and the stream gets a chunk for each row.

The middleware should follow routes and the stream must be attached to the request object as req.resultStream.

If req.resultStream is not present or is not a ReadableStream the middleware does nothing and just forwards to next.

The middleware assumes that the entire response represents an array and that each row in the array is a json string or a buffer representing the same. The middleware transforms the stream by prepending the first chunk with "[", adding a comma after each chunk except the last, and appending "]" after the last chunk is received.

The transformed stream is piped to res so the res can start streaming as soon as it gets the first row of data.

##Installation VERSION 4 is likely broken

npm install express-stream-json

##Usage In app.js add the following line after the routes section

use require("express-stream-json")

In the processing that your routes call attach the stream to be processed:

...
req.resultStream=MyStream
...
next();

If you are not using an array stream just use the normal method of sending results and do not create req.resultStream. The middleware will then do nothing.

res.send(results);
next()

Obviously the middleware is only useful for browsers which can handle chunked responses so it is of no use for IE8 and earlier.

Even if the client does not expose the results until the entire response is received using the middleware still offers the advantage of reduced memory and less latency in the the start of the response.