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

@trenskow/results

v0.1.6

Published

Executes an array of promises and returns their resolved or rejected results.

Downloads

36

Readme

@trenskow/results

Executes an array of promises and returns their resolved or rejected results.

Installation

npm install --save @trenskow/results

Usage

const results = require('@trenskow/results');

Getting all Results

const [resolved, rejected] = results([
	Promise.resolve('a'),
	Promise.reject(new Error('a')),
	Promise.resolve('b'),
	Promise.reject(new Error('b'))
]);
/* -> [['a','b'],[Error('a'), Error('b')]] */

Getting Only Resolved Results

const resolved = results.resolved([
	Promise.resolve('a'),
	Promise.reject(new Error('a')),
	Promise.resolve('b'),
	Promise.reject(new Error('b'))
]);
/* -> ['a','b'] */

Getting Only Rejected Results

const rejected = results.rejected([
	Promise.resolve('a'),
	Promise.reject(new Error('a')),
	Promise.resolve('b'),
	Promise.reject(new Error('b'))
]);
/* -> [Error('a'),Error('b')] */

Order

The promises are executed in serial and therefore out-of-order, meaning there is no guarantee in which order the result comes out.

Executing in Parallel

You can specify how many promises can be executed at once by using an option.

const [resolved, rejected] = results(/* promises */, { simultaneously: 1 });

The above example will make the promises execute one at the time (which also guarantees order). You can specify any arbitrary number, default is 0, which is equal to unlimited.

This works for all three variants (resolved/rejected, resolved and rejected).

LICENSE

MIT (see license).