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

promise-accum

v1.6.0

Published

Solve variable scoping and/or callback hell in promises

Downloads

29

Readme

Installation

npm install promise-accum

Motivation

Often when using promises, variable scoping becomes an issue, specifically when doing an operation that requires something along the lines of "load two things in the database, then do something based on that".

There are a few ways to solve this problem:

  1. Stay in callback hell

    LoadItemOne().then(function(item1) {
    	return LoadItemTwo().then(function(item2) {
    		return DoSomethingWithItems(item1, item2);
    	});
    });
  2. Enter variable scoping hell

    var item1;
    LoadItemOne().then(function(i) {
        item1 = i;
        return LoadItemTwo();
    }).then(function(item2) {
    	return DoSomethingWithItems(item1, item2);
    });
  3. Return ugly objects

    LoadItemOne().then(function(item2) {
        return LoadItemTwo().then(function(item2) {
            return { item1: item1, item2: item2 }
        });
    }).then(function(items) {
    	return DoSomethingWithItems(items.item1, items.item2);
    });

This library provides a solution. Context is stored in a variable called $. To add the result of a promise to the context, call $('key'). In this case:

var $ = require('promise-accum');

LoadItemOne().then($('item1')).then(function($) {
    return LoadItemTwo().then($('item2'));
}).then(function($) {
	return DoSomethingWithItems($.item1, $.item2);
});

Error handling

Using this solution, the context object must be passed through the entire chain:

LoadItemOne().then($('item1')).then(function($) {
    $.item1.foo = 'bar';
}).then(function($) {
    // $ is not the context, obviously.
});

In most cases, it's as simple as returning $ in the promise. However, in some promise libraries (q and bluebird, among others), errors can be handled by calling .catch(errorHandler). This is effectively an alias for .then(null, errorHandler) – of course, in this case, the context does not get passed through, so any functions after the error handler it.

To mitigate this, promise-accum provides $.passthrough:

LoadItemOne().then($('item1')).then($.passthrough, errorHandler).then(function($) {
    // $ is maintained.
});