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

kue-chain

v1.0.2

Published

Chain Kue jobs.

Downloads

16

Readme

kue-chain

Using Kue I discovered that most of the new jobs in my system are created on reaction to some other jobs finish. After implementing a little helper function it got a little better, but it still left a lot of repetetive parts in the code which managed the sequencing of jobs. So I went a little further to make what's happening on what more clear. This is what came out.

Installation

npm install kue-chain

Usage

First define your job types which inherit from Kue.Job:

var Job = require('kue').Job;
var util = require('util');

function TakeApart(thing) {
    Job.call(this, 'takeapart', {
        thing: thing
    });
}
util.inherits(TakeApart, Job);

function Repair(pieces, takeApartJobData) {
    Job.call(this, 'repair', {
        thing: takeApartJobData.thing,
        parts: pieces
    });
}
util.inherits(Repair, Job);

[...]

Start combining:

var kue = require('kue');
var jobs = kue.createQueue();
var when = require('kue-chain')(jobs, kue.Job);

when(TakeApart).then(Repair);
when(Repair).then(PutBackTogether);

Sometimes a little more control is needed:

/*
    ensure GoToStore and Buy are Kue Jobs...
 */
when(GoToStore).then(function (result, job.data, job, then) {
    checkTheShoppinglist(function (list) {
        // Buy each of the list items
        list.forEach(function (item) {
            then(new Buy(item));
        });
        // Always buy beer
        then(new Buy('beer'));
    });
});

And at other times you just need a shortcut to creat them:

var takeApartJob = new TakeApart('scooter');
takeApartJob.save();

Api

Module exports a function. The chainer:

chainer(Kue.Queue queue, Kue.Job KueJob) -> Function when(string|Function ParentJob)

This is needed for setup and setting up the job complete listener.

when(string|Function ParentJob) -> Object thenable

Function takes a parent job as well a string for the job type and returns a object with one property: then.

Object thenable.then(Job|Function job) -> void

Function takes a child Job, which, as well as ParentJob, has to inherit from the Kues Job prototype, or a function job(result, Object completedJobData, Job completedJob, Function then). then function here takes instance of a job and saves it.