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

job-pool

v0.19.0

Published

manage a queue of workers and work to do

Downloads

8

Readme

job-pool is yet another module for managing a pool of work and a number of asynchronous workers.

The thing that makes it unusual is that rather than encoding tasks as strings or some other serialized form, jobs are callbacks.

So, if you want a worker to add up some numbers:

function addNumbers(callback) {
  var result = 1 + 2 + 3
  callback(result)
}

You pass that function to the pool:

var JobPool = require("job-pool")

var jobPool = new JobPool()

jobPool.addTask(
  addNumbers,
  function(result) {
    // result will be 6
  }
)

In order for the result to actually be calculated, you need to register a worker:

jobPool.requestWork(
  function(task) {
    // at the worker's leisure, they can call the function:
    task.func(function(result) {
      // and then report back the result:
      task.callback(result)
      // at that point they'll be registered for more work
    })
  }
)

Retaining workers

If you want to have a single worker do multiple tasks, you can retain them:

var myWorker = jobPool.retainWorker()

myWorker.addTask(
  doThis,
  function() {
    myWorker.addTask(another, done)
  }
)

function doThis(callback) { callback () }

function another(callback) { callback () }

function done() {}

Providing data

You can send a data payload to the worker as well, for them to apply to the function:

jobPool.addTask(
  function(callback) {
    callback("one")
  }, function ok() {
    done()
  },
  {birdie: "toot toot!"}
)

jobPool.requestWork(
  function (task) {
    expect(task.options.birdie).to.equal("toot toot!")
    task.callback()
  }
)