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-rejected

v1.0.0

Published

Return rejected promises

Downloads

4

Readme

promise-rejected

NPM version build status Test coverage Downloads

Wait for an array of promises to be completed (resolved or rejected) and return an array with only the rejections.

Installation

$ npm install promise-reject

or

$ yarn add promise-reject

Why ?

Promise.all will stop at first error detected while promise-rejected will give run all the promises and return all errors detected.

As its goal is to detected errors, the promise is resolved with detected errors.

Usage

promise-rejected is useful when you need to have access to a list of errors.

A good example is like in form validation. If you have a validation function for each field, any invalid field might throw an error that you can catch.

promise-rejected will enable you to display an error for all invalid fields in one row while using Promise.all will enable you to only display the first invalid field.

Example

This example is a bit contrived but you should understand the purpose of the promise-rejected function.

const rejected = require('promise-rejected')

rejected([1, 2, 3, 4, 5, 6].map(function (v) {
  if (v % 2 === 0) {
    throw new Error('invalid value')
  }
}))
  .then(function (val) {
    val.map(function (err) {
      console.log('Error : #' + err.message)
      /*
        Error : #2
        Error : #4
        Error : #6
      */
    })
  })
  .catch()

If you had used Promise.all the promise chain will have been rejected with only the first error :

Inspiration

License

MIT