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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@sumanion/queue

v1.2.0

Published

Fast, unopinionated, minimalist queue manager for Node.js

Downloads

0

Readme

Queue Manager

Fast, unopinionated, minimalist queue manager for Node.js

Installation

Using npm:

$ npm install @sumanion/queue --save

Using yarn:

$ yarn add @sumanion/queue

Usage

// Load the module.
const queue = require('@sumanion/queue')

// Create a queue manager with default options.
const q = queue.create()

// Or set custom options.
const q = queue.create({
  // Maximum number of concurrent active tasks.
  max: 1, // Accepted values: 1..Infinity
  // Queue manager will automatically start to run tasks.
  start: true // Accepted values: true or false
})

// Set the maximum number of concurrent active tasks.
q.max(1)

// Start the queue manager.
q.start()

// Stop the queue manager.
q.stop()

// Return the number of tasks in the queue.
q.size()

// Show the number of active tasks.
q.active()

// Remove all queued tasks.
q.clear()

// Add a new task to the queue.
q(next => {
  // The task contents.
  console.log(1)

  // IMPORTANT: When the task finishes it's job you should
  // always call the `next()` method to start the next task.
  next()
})

// Add another task to the queue.
q(next => {
  // The task contents.
  console.log(2)

  // NOTE: You can wait as long as you need before you call
  // the `next()` method.
  setTimeout(() => {
    // IMPORTANT: When the task finishes it's job you should
    // always call the `next()` method to start the next task.
    next()
  }, 1000)
})

// The queue manager will output:
// 1
// 2

Task Priorities

  • High Priority Tasks - are executed before all other tasks. If there are many high priority tasks they are executed in the order they were added to the queue manager.
q.high(next => {
  next()
})
  • Normal Priority Task - are executed after all high priority tasks. If there are many normal priority tasks they are executed in the order they were added to the queue manager.
q(next => {
  next()
})
  • Low Priority Tasks - are executed after all high priority and normal priority tasks. If there are many low priority tasks they are executed in the order they were added to the queue manager.
q.low(next => {
  next()
})

Important Notes

  • Queue manager will always keep the tasks in the order you added them.
  • You should always call the next() method manually when your tasks finish to do their jobs.

Possible Issues

  • next() method inside a task must be called exactly one time, because it decreases the number of currently active tasks by one and if you call it multiple times it will run the wrong number of concurrent tasks. Of course it will back to normal shortly, but you should be aware of this side effect.
  • If you will not call the next() method on a task when it finishes it's job, queue manager will not start another tasks, it will wait forever the previous task to finish.

License

MIT