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-try-catch

v0.0.2

Published

Simulate a try catch on a stream pipeline

Downloads

10

Readme

stream-try-catch

a try-catch like library for stream pipelines

build status

Example

try catch errors on a pipeline

var _try = require('stream-try-catch').try;

// pipe streams
var stream = _try(streamA).pipe(streamB).pipe(streamC).catch(onerror);

// regular piping takes place
assert(stream == streamC);

// propagates errors
var onerror = function(err) {
  // called three times
});

streamA.emit('error', new Error);
streamB.emit('error', new Error);
streamC.emit('error', new Error);

API

try(src)

Begin the setup of try/catch sequence on a pipeline

Any call to try(src).pipe(dest, opt) will automatically

  • forward all 'error' events from src to dest.
  • make sure dest is instrumented in the same way (just as if try(dest) had been called)

you can catch errors on the pipeline either by adding a classic on('error', onerror) on the last stream of the pipeline or use the syntactic sugar catch

try(streamA).pipe(streamB).pipe(streamC).catch(onerror);

This will forward all errors from streamA, streamB and streamC to onerror

Note that a catch stops the try/catch block so in

var stream = try(streamA).pipe(streamB).catch(onerror).pipe(streamC);

the errors from A and B will bubble to onerror but they will not bubble to streamC.

In a way, the try/catch guards

Installation

$ npm install stream-try-catch

Licence

MIT