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

error-handling

v1.0.0

Published

error-handling ==============

Downloads

21

Readme

error-handling

At VirtuOz we love Futures. But when you use it, you end up with lots, and I do mean lots, of boilderplate error-handling code. Like this:

var Future = require('futures').future;
.
.
.
function doSomethingInTheFuture()
{
    var future = new Future()

    someAsynchronousOperation(function(err, result)
    {
        if (err)
        {
            future.fulfill(err);
            return;
        }

        // Now do something else.
        somethingElseAsynchronous(function(err, anotherResult)
        {
            if (err)
            {
                future.fulfill(err);
                return;
            }

            var myOperationResult = result + anotherResult;
            future.fulfill(undefined, myOperationResult);
        });

    });
    return future;
}


var futureResult = doSomethingInTheFuture();
futureResult.when(function(err, result))
{
    // Code to handle async return.
});

As you can see, the code to handle errors is boring and repetitive. Enter this module. It will save you time. And make you happy. Like this:

var Future = require('futures').future;
var eh = require('vnodelib').load('error-handling');
.
.
.
function doSomethingInTheFuture()
{
    var future = new Future()
    var wrap = eh.createWrapperFromFuture(future);

    someAsynchronousOperation(wrap(function(result)
    {
        // Now do something else.
        somethingElseAsynchronous(wrap(function(anotherResult)
        {
            var myOperationResult = result + anotherResult;
            future.fulfill(undefined, myOperationResult);
        }));

    }));
    return future;
}


var futureResult = doSomethingInTheFuture();
futureResult.when(function(err, result))
{
    // Code to handle async return.
});

See? Lots of boilerplate cut out of the picture.

Of course, you needn't just use error-handling with Future. You can do it like this:

var eh = require('vnodelib').load('error-handling');
.
.
.
function doSomethingInTheFuture(callback)
{
    var wrap = eh.createWrapperFromCallback(function(err)
    {
        // Custom logging or whatever goes here.

        // Tell the callback that something really bad happened.
        callback(err);
    });

    someAsynchronousOperation(wrap(function(result)
    {
        // Now do something else.
        somethingElseAsynchronous(wrap(function(anotherResult)
        {
            var myOperationResult = result + anotherResult;
            callback(undefined, myOperationResult);
        }));

    }));
    return future;
}

If you're still not convinced, try using Future or even the standard async pattern where errors are involved, for anything other than a trivial example. You'll be sad. Then you can come back here. And be happy.