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

node-taskqueue

v0.0.3

Published

A simple framework for producing and distributing tasks

Downloads

3

Readme

node-taskqueue

Uses redis to distribute tasks among any number of workers. Workers have the ability to communicate results back to the initiator.

TODO

Create an NPM package.

Usage

see the examples directory

create your tasks file (testTasks.js)


var Tasker = require('./tasker.js').Tasker;
var tasker = new Tasker();

tasker.registerTask('add', function(data, done) {

    /* The first arg to done is any error
     * the second is the result of the task
     */

    done('', data.first + data.second);
});

module.exports.testTasks = tasker;
    

create your worker file (workerTest.js), running this file will create a worker process that polls the local redis server for task requests


#!/usr/bin/env node

var Worker      = require('./tasker.js').TaskWorker;
var testTasks   = require('./testTasks.js').testTasks;

var worker = new Worker({tasks: testTasks});

open a shell, nav to folder, do: (leave it going) node workerTest.js

produce some work for the worker (testProducer.js)


#!/usr/bin/env node

var testTasks   = require('./testTasks.js').testTasks;

function logIt(err, res) {
    console.log(res);
}    

/* Because we pass a callback, the callback will be
 * called with the result of our workers' work.
 * the delayed.add means that the task is pushed
 * to redis for distribution to workers
 */
testTasks.tasks.add.delayed({first:1,second:2}, logIt);
testTasks.tasks.add.delayed({first:2,second:3}, logIt);

/* of course we can run the task locally too */
testTasks.tasks.add.now({first:1, second:2}, logIt);

/* if we pass no callback, then the result is discarded */
testTasks.tasks.add.delayed({first:7,second:13});

open another shell, nav to examples folder: node testProducer.js

you should see some combination of 3, 5, and 12 being printed