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

p-seq

v1.1.0

Published

Run async tasks sequently

Downloads

5

Readme

p-seq Build Status Coverage Status

Run async tasks sequently

Install

$ npm install --save p-seq

Usage

const pSeq = require('p-seq');

// op1, op2, op3 is functions that return a Promise.
pSeq(op1, op2, op3)
  .then(result => {
    // Get the result of last task here.
  })
  .catch(err => {
    // Reach here if any error thrown.
  });

When the Promise of a task resolved, p-seq passes its result to next task generator. So there will be only one task is running at one time.

API

pSeq(tasks)

Arguments

  • tasks: An array of task generators, element type is Promise, Function or GeneratorFunction.

Return Value

A Promise represented the last task.

Discussion

When a task generator is Promise, p-seq just pass its result to next task. When it is a function or generator function, p-seq call it when last task is resolved, and pass the result of last task to it, the function should return a Promise, otherwise p-seq just pass the return value through. Since the generator is run via co, it produces a Promise intrinsically.

If a task generator's type is none of above, p-seq just pass itself through the chain, but we strongly recommend you to avoid doing that.

There is also a more convenient way to pass tasks:

pSeq(task1, task2, ...)

License

MIT © Cyandev