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

atlas-waterfall

v1.0.0

Published

Run async functions in a "waterfall" series with an onDone callback.

Downloads

4

Readme

atlas-waterfall

Run async functions in a "waterfall" series with an onDone callback.

Travis


install

npm install --save atlas-waterfall

why

If you want to avoid promises, you can use a waterfall instead. It will run an array of N async functions in serial, passing the (err, ...results) from one function to the next. The allDone callback receives the (err, ...results) from the very last function. See examples below.

examples

array of jobs

The following will run reddit.post with the results/error from email.send, and the final callback with the results from reddit.post:

const waterfall = require("atlas-waterfall");
waterfall([
  done => email.send("[email protected]", "hello", (emailErr, isSuccess, id) => {
    // can pass many results to next job in the waterfall
    if (emailErr) return done(emailErr, "failed early...")
    done(null, isSuccess, id)
  }),
  (done, isSuccess, id) => {
    const subreddit = isSuccess ? "mildlyinteresting" : "mildlyinfuriating"
    reddit.post("atlassubbed.png", subreddit, postErr => {
      done(postErr, "tried", "all tasks");
    })
  }
], (err, ...res) => {
  // if email failed: err === emailErr, res === ["failed early..."]
  // if post failed: err === postErr, res === ["tried", "all tasks"]
  // if no errors: err === null, res === ["tried", "all tasks"]
})

caveats

If any function in the sequence returns an error, the remainder of the sequence will be skipped, and the allDone callback will be called with the error. Sometimes, a task will fail but you will still need to run the remaining functions -- in this case, simply handle the error instead of passing it as the first argument to the task's done callback.

todo

Passing initial args might be useful:

waterfall(...args, [
  (done, ...args) => {

  },
  ...otherJobs
], allDone)

It would be more symmetric and aesthetic to allow initial args to be passed to the first job, since the last job's results are passed to allDone. Of course, this can easily be done with a jobs factory, so I don't think it's needed:

waterfall(getJobs(...args), allDone)