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

@tmurphree/promise-all-settled-plus

v2.0.0

Published

Add helper functionality to Promise.allSettled

Downloads

5

Readme

promise-all-settled-plus

Adds useful getters to the result of a call to Promise.allSettled.

Prerequisites

|Prerequisite|Comments| |---|---| |Requires Promise.allSettled to exist.|This shouldn't be a problem for most users. It's in Node.js 12.13.0 and most major browsers (see caniuse.com, April 22, 2020), so most people won't have a problem. Please create an issue and I'm open to working on this with you if you need it to work with a custom Promise library.

Accepts

An array of Promises.

Input is validated for an array of native Promises. If you use a module that uses another Promise library, you may need to bypass this check with the checkInputForPromises option:

promiseAllSettledPlus([customPromise1, customPromise2], { checkInputForPromises: false })
// etc

Returns

Returns a Promise that resolves to a plain JavaScript object:
/**
 * @typedef {object}
 * @property {boolean} areAllFulfilled true if every Promise is fulfilled.
 * @property {boolean} areAllRejected true if every Promise is rejected.
 * @property {number} fulfilledCount
 * @property {boolean} hasFulfilled true if at least one Promise is fulfilled.
 * @property {boolean} hasRejected true if at least one Promise is rejected.
 * @property {object[]} rawResult The raw result from the Promise.allSettled call.
 * @property {number} rejectedCount
 */

e.g.
{
  areAllFulfilled: false,
  areAllRejected: false,
  fulfilledCount: 2,
  hasFulfilled: true,
  hasRejected: true,
  rawResult: [
    { status: 'fulfilled', value: 42 },
    { status: 'fulfilled', value: 99 },
    { status: 'rejected', reason: (new Error('Request timed out')) }
  ],
  rejectedCount: 1,
}

Usage

Require this module and call promiseAllSettledPlus wherever you'd call of Promise.allSettled.

const promiseAllSettledPlus = require('@tmurphree/promise-all-settled-plus');

promiseAllSettledPlus([thisReturnsApromise(), soDoesThis()])
  .then((result) => {
    if (result.hasRejected) { 
      // do something
    }

    // more code goes here
  })
  .catch(errorHandler);

Edge case

promiseAllSettledPlus([])

// resolves to:
{
  areAllFulfilled: false,
  areAllRejected: false,
  fulfilledCount: 0,
  hasFulfilled: false,
  hasRejected: false,
  rawResult: [],
  rejectedCount: 0,
}

Explanations

Why do I have to use an array when Promise.allSettled takes an iterable?

We get weird results when we use iterables other than arrays in Promise.allSettled.
This doesn't fail:

const myMap = new Map([
  [1, Promise.resolve(2)],
  [2, Promise.reject(new Error('some error'))],
]);


Promise.allSettled(myMap)
  .then((result) {
    // result is now: 
    // [
    //   { status: 'fulfilled', value: [ 1, [Promise] ] },
    //   { status: 'fulfilled', value: [ 2, [Promise] ] }
    // ]
  })
  .catch(console.error);

But it also didn't give the expected result. You were probably expecting:

[
  { status: 'fulfilled', value: 2 },
  { status: 'rejected', value: new Error('some error') }
]

If you want to use Maps or other iterables in this library natively, please create an issue and I'm open to working on this with you.