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

qued

v0.0.10

Published

A simple worker queue that works.

Downloads

26

Readme

qued

Circle CI

A very simple queue/dequeue worker inspired by kue. In fact, it is so similar that it is essentially a drop-in replacement. It runs on Node.js applications and requires Redis for storage.

This queue has a mantra of "simplicity over functionality" where we want less complexity in code and more stability in the worker. Therefore, there is no extra queues (like completed and error) and executes one job at a time.

install

npm install qued --save

usage

To create an instance of qued:

var Qued = require('qued');
var qued = new Qued({
  REDIS_HOSTNAME: 'localhost',
  REDIS_PORT: 6379,
  REDIS_PASSWORD: null,
  TIMEOUT: 0
});
  • TIMEOUT
    • the maximum amount of time a job has to execute in milliseconds
    • set to 0 for no timeout
    • useful if your jobs are poorly written and forget to call the cb() function
    • prevents your workers from getting clogged

To create a consumer that will push jobs on the queue.

var jobs = qued.createConsumer();

jobs.create('job_name', {data:'data'}).save(function(){});

Your worker that will execute jobs from the queue, looking something like this.

qued.addProcess('job_name', function(job, done) {
  setTimeout(done, 100);
});

var worker = qued.createWorker();

extras

To prevent your worker from stopping mid execution, you can implement use the shutdown function which ensures that the last job executing finishes.

process.on('message', function(message) {
  if (message === 'shutdown') {
    worker.shutdown(function() {
      process.exit(0);
    });
  });
});

license

MIT.