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

workq

v3.0.0

Published

A super tiny work queue

Downloads

5,560

Readme

workq

js-standard-style Build Status Coverage Status

A super tiny work queue.

It can handle nested queues, the order of execution is guaranteed.
The top level queue will start automatically once you add at least one job in the queue, the nested queues will start once the done callback has been called; you cannot add more jobs in the current queue after done has been called.

If you need a shared queue between multiple files pass the option { singleton: true } in every file you need it.

Install

npm i workq --save

Usage

const q = require('workq')()

q.add(job)

function job (child, done) {
  // perform some work
  // you can add nested jobs!
  child.add(nestedJob)
  done()
})

function nestedJob (child, done) {
  // perform some work
  done()
})

Async/await and promises are supported as well!

const q = require('workq')()

q.add(job)

// there is no need to call `done`!
async function job (child) {
  // perform some work
  // you can add nested jobs!
  child.add(nestedJob)
})

async function nestedJob (child) {
  // perform some work
})

If you need to know when a queue has finished all its jobs, you can use the drain api.
Note that in the top queue the drain hook can be called multiple times.

const q = require('workq')()

q.drain(done => {
  // the current queue has finished its jobs
  // async await is supported as well
  done()
})

q.add(job)

function job (child, done) {
  // perform some work
  // you can add nested jobs!
  child.add(nestedJob)
  done()
})

function nestedJob (child, done) {
  // perform some work
  done()
})

If you need to pass some parameter to the job, just add them after the function in add:

const q = require('workq')()

q.add(job, 'hello', 42)

function job (child, greeting, num, done) {
  console.log(greeting, num) // 'hello' 42
  done()
})

If needed you can also use the child method to create custom child queues. The child queues will be executed once the current queue has finished its execution.

const q = require('workq')()

const childq = q.child()

q.add(job, 'hello', 42)
childq.add(job, 'hello', 42)

function job (child, greeting, num, done) {
  console.log(greeting, num) // 'hello' 42
  done()
})

License

Licensed under MIT.