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

safe-readable-stream

v0.2.10

Published

Wrapper for reliable work for stream.Readable

Downloads

10

Readme

Wrapper on Node.js stream.Readable().

Promise based work with stream.Readable() for safe pushing data into the stream.

E.g. you can use:


const rStream = require('safe-readable-stream');

const outStream = rStream.createSafeReadableStream({
  logger,
  objectMode: false,
});

// Good, await will wait until stream will be ready to read next chunks.
await outStream.pushArray(['A', 'B', 'C']);

// Pushing next chunk.
// But without wait. Not good.
// Next push can return rejected promise
// if underlying push will require next event loop tick.
outStream.push('B');

// Promise can be rejected.
// Because it is not safe to push data outside _read call.
await outStream.finish();

Catching an error sent by outStream.error(msg):

It is useful when you are reading some data from some source by chunks and at some soment you got error from the source. So you should pass the error to the receiving part.

So for receiving part you can use such code:


const rStream = require('safe-readable-stream');

response.on('data', (data) => {
  const errStr = rStream.checkErrorString(data);
  if (errStr) {
    // Error was sent.
    l.println(`Checked error string: ${errStr}`);
  }
});