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

limited-queue

v1.0.1

Published

An extended version of async.queue which allows to specify a maximum number of total jobs that are expected to be executed

Downloads

3

Readme

limited-queue

Limited queue provides an augmented version of async.queue. A limited queue has a specified maximum number of tasks it accepts and processes. An optional callback is executed after the last of the tasks was completed. Everything else works like async.queue.

Usage

The syntax to create a limited-queue: queue(worker, [concurrency], maxTaskCount)

Arguments

  • worker(task, callback, currentTaskCount): The worker that processes the tasks that are pushed to the queue (see async.queue). The additional parameter currentTaskCount is an Integer containing the number of tasks that were already completed by the queue.
  • concurrency: The number of tasks that may be processed in parallel (see async.queue). Can be omitted.
  • maxTaskCount: The maximum number of tasks the queue accepts. Any tasks that will be pushed to the queue after this threshold is reached will not be processed. Instead, the tasks callback method will be called with an error message as first argument. Failed tasks will also count as completed tasks.

Queue objects (in addition to async.queue)

  • finaldrain(currentTaskCount): A callback that will be called once after the specified maxTaskCount was reached, and all tasks were completed. The parameter currentTaskCount provides the number of tasks that were completed. It will be equal to the maxTaskCount if all tasks complete successfully.
  • currentTaskCount: An Integer to determine how many tasks were completed yet.

Example

var limitedQueue = require('limited-queue');

function worker(data, callback) {
    console.log(data);
    callback();
}
var concurrency = 5;
var maxTaskCount = 2;

var queue = limitedQueue.queue(worker, concurrency, maxTaskCount);

queue.finaldrain = function(taskCount) {
  console.log(taskCount+" tasks completed");
}

queue.push("data1"); // push first task to worker
queue.push("data2"); // push second task to worker, will trigger `finaldrain` after completion because `maxTaskCount` is 2
queue.push("data3"); // will not bee pushed to the worker because `maxTaskCount` is 2