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

promises-all

v1.0.0

Published

Track down promise states of all promise functions executing in parallel. Similar to promise.all function, but it rejects the complete promise.all() even if any one of the promise fails, where as promises-all npm will indiviudally return you the states.

Downloads

19,887

Readme

Build Status Known Vulnerabilities

promises-all

Track down promise states of all promise functions executing in parallel. Similar to promise.all function, but it rejects the complete promise.all() even if any one of the promise fails, where as promises-all npm will indiviudally return you the states.

If you have used promises in your javscript code, then you might know one very good functionality of it, that is promise.all(). Fires multiple promise calls in parallel! Awesome!!

Recently I got stuck wiht this. My requirement was to fire 3 API calls parallely, but don't really care if any one of the api calls fail, unless all of them are failing! Then thats a different story. But, i could not achieve this, because promise.all rejects all the promise even if any on of them rejects.

There are solutions one would suggest that dont reject your indiviudal functions, rather always resolve them and then check once promise.all is done with all promise calls. But then why should I move that logic of checking fail case outside the function which is actually making an API call. Doesnt make sense to me.

Hence, I wrote a small plugin as well as an npm package which does exacltly what I explained earlier.

Promises-all will always resolve, irrespective of any promise calls rejects or resolves. Yes, it will reject also but only if there is some exception in the code!

It uses bluebird as the promise library when in node.

Below is the example:

Require:

var PromiseAll = require('promises-all');

Sample Call:

PromiseAll.all([p1(), p2()]).then(function(response) {
	console.log(response);
}, function(error) {
	console.log(error);
});

function p1() {
	return new bluebird(function(resolve, reject) {
		setTimeout(function() {
			resolve('p1 resolved');
		}, 1000);
	});	
}

function p2() {
	return new bluebird(function(resolve, reject) {
		setTimeout(function() {
			reject('p2 rejected');
		}, 3000);
	});	
}

Output:

{
	resolve: [ 'p1 resolved' ],
	reject: [ 'p2 rejected' ] 
}