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

errback

v1.0.0

Published

Pass standard error-first callbacks to functions that expect result-first callbacks

Downloads

3

Readme

errback

Error-first callbacks everywhere!

What?

So, because you're a decent, considerate human being, you write all of your callbacks in this format:

function callback(error, result) {
    if (error) { throw error; }

    console.log(result);
}

Good for you. You play well with others. High five from me.

Some APIs aren't as considerate...

They'll just go ahead and pass their result as the first argument to your callback:

function badAPI(callback) {
    var result = 10;

    return callback(result);
}

...giving you no way to consistently tell if an error occurred.

badAPI(callback);

// BOOM! Your callback just threw
// something that wasn't an error!

What assholes, eh?

errback takes your error-first callback and returns a function that you can use with these terrible APIs. When it gets called, your original callback will be called with null as the first argument, and the original result as the second argument:

badAPI(errback(callback));

// > 10

Ahhhh, much better.