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 🙏

© 2026 – Pkg Stats / Ryan Hefner

rescue-error

v0.0.9

Published

A small API that allows branching on error handling based on specific rules.

Readme

rescue-error

When dealing with operations with multiple scenarios for error, one often needs to do some checking on the result error before taking action. Usually one takes different actions based on these checks.

rescue-error tries to simplify this branching process through a cohesive fluent API.

Basic Usage

const Rescue = require('rescue').Rescue;


// Something went wrong and we have an Error (or a subtype of it)
//
// err => 'Some error message.';

new Rescue(err)
        .ifAttribute('somePropertyName', _ => 'Do something about this error if it has the given property and it\'s truthy.')
        .ifMessage(/message/, _ => 'Do something about this error.')
        .default(_ => 'Do this in case none of the rules matches.')
        .do(); // Attempts to apply the rules.

Remarks about the do() operation

The do operation marks the end of configurations and performs the checks on the different rules and applies the matched predicate, if any. Some important points to consider about this are:

  • It will throw an Error itself if none of the provided rules matched and there was not a default rule to fall back to.

  • It will execute ONLY ONE of the branches, even though if multiple ones apply. In this case the first one that satifies its condition.

Basic Rules Available

ifAttribute

Executes the provided predicate function if the designed attribute name exists on the Error object and holds a truthy value.

ifMessage

Executes the provded predicate function if message attribute of the Error tests positive against the given Regular Expression.

ifType

Executes the provided prediate function if the Error in context is an instance of the designed type.

default

Designates a predicate to fall to if none of the attempted rules applies. The order in which this is called with regards to other rules is not relevant.