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

if-error

v1.0.6

Published

Helps automate error handling in Node.JS applications.

Downloads

27

Readme

If Error

Helps automate error handling in Node.JS applications.

Install

npm install if-error

Source code is at https://github.com/jeffersoncarpenter/if-error.

Example

Async operations can often experience errors. These errors are endemic to the world at large, not due to bugs in the code. Still, we write boilerplate in the form of if (err) { return next(err) }, catching these relative low-level errors one by one. Because such errors are rare, they lead to subtle bugs that are difficult to track down.

var middleware = function (next) {
  return asyncOperation1(function (err, result1) {
    if (err) { return next(err); }
    return asyncOperation2(result1, function (err, result2) {
      if (err) { return next(err); }
      return asyncOperation3(result2, function (err, result3) {
        if (err) { return next(err); }
        return next(null, result3);
      });
    });
  });
};

This tiny library greatly increases the robustness of this boilerplate code. Rather than a boilerplate if statement, you declare your error handler - and then make boilerplate calls to it. If you use this style everywhere, err values will only appear in your logging code.

var handleErrWith = require('if-error');

var middleware = function (next) {
  var handleErr = handleErrWith(next);
  return asyncOperation1(handleErr(function (result1) {
    return asyncOperation2(result1, handleErr(function (result2) {
      return asyncOperation3(result2, hanldeErr(function (result3) {
        return next(null, result3);
      }));
    }));
  }));
};