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

readable-valve

v0.3.3

Published

subscribe to filtered emits of readable streams

Downloads

10

Readme

readable-valve

build status AppVeyor Build Status Security Responsible Disclosure


Subscribe to filtered emits of readable streams.


Get it!

npm install --save readable-valve

Usage

const createReadableValve = require('readable-valve')
const { PassThrough } = require('stream')

const passthru = new PassThrough()

createReadableValve(passthru, chunk => !/fraud/.test(chunk))
  .subscribe(chunk => console.log(String(chunk)))
  .onerror(console.error)

for (const msg of [ 'hi', 'fraud', 'blabla', 'bye' ]) passthru.write(msg)

The valve will filter out all messages that contain the string 'fraud'.


API

valve = createReadableValve(readable[, pred])

Create a valve for a readable stream that filters according to a predicate function. If the predicate is not passed at instantiation it must be provided in any calls of valve.subscribe.

valve.subscribe(listener[, pred][, n])

Subscribe a listener to the valve. If no predicate was passed at instantiation it must be provided here. If a predicate was passed at instantiation and also to a call of valve.subscribe, the latter takes precedence. The trailing parameter can be used to limit the number of listener calls.

You can register various predicate listeners with a readable stream using only one valve by specifying distinct predicates in valve.subscribe calls.

valve.unsubscribe(listener)

Unubscribe a listener from the valve.

valve.onerror(listener[, n])

Handle errors of the underlying readable stream. Setting the trailing parameter to a positive number limits the number of listener calls.

The valve itself does not generate errors. All errors emitted by a valve are simply forwarded from the underlying readable stream. Thus, the valve.onerror method should primarily be used to attach error listeners to readables which do not have any error listeners registered with themselves.

valve.unerror(listener)

Unregister the passed error listener.


License

MIT