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

async-find

v1.1.0

Published

Evaluate an array of asynchronous functions, one by one, until one resolves.

Downloads

3

Readme

async-find

Based upon the behaviour of Array.find, an asynchronous function which iterates an array of asynchronous functions (or Promises), one by one sequentially, evaluating each one in turn until one resolves.

As soon as one resolves, the resolved response is returned and the process halts.

If all functions reject, the function itself rejects with a specific ExhaustionError. This can be identified by checking the code property on the error object equals ERR_FUNCTIONS_EXHAUSTED.

ExhaustionError objects have an internalErrors property, an Array of each rejected error that occured whilst iterating the Promises.

Example

const asyncFind = require('async-find');

async function rejectingAsyncFunction(i) {
  console.log(i);
  throw new Error();
}

async function resolvingAsyncFunction() {
  return 'Resolved!';
}

asyncFind([
  () => rejectingAsyncFunction(1),
  () => rejectingAsyncFunction(2),
  resolvingAsyncFunction,
  () => rejectingAsyncFunction(3),
])
  .then(console.log);

Will return:

1
2
Resolved!

The final function is never called, because the previous function resolved.

Author

License

MIT