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

firework

v1.1.0

Published

A distributed, fault-tolerant work queue for Firebase

Downloads

25

Readme

npm package build status dependency status code climate

Firework is a distributed, fault-tolerant work queue for Firebase.

Creating Jobs

Since you're using Firebase, you'll probably want to create jobs directly from the browser. To do this, setup a new Firebase location reference that will serve as your queue. To start, you may want to make sure that this location is writable by everyone but only readable by your server (i.e. worker) process.

In this example, we'll assume that your queue is located at https://my-firebase.firebaseio.com/myQueue. In your client code, you'll want to create a new child of the pendingJobs child of that location reference, like so:

var jobs = new Firebase('https://my-firebase.firebaseio.com/myQueue/pendingJobs');
jobs.push({ my: 'job' });

That's it. You've now pushed a job onto the queue for a worker to process sometime later.

It should be noted that workers pull from the beginning of the queue (FIFO). If you have jobs of varying importance you can use a priority to run some jobs before others.

jobs.push().setWithPriority({ important: 'job' }, 0);
jobs.push().setWithPriority({ less: 'important' }, 100);

Firework also provides an API for creating jobs from within your server process. A Firework.Queue (see below) has a push method for this purpose.

var queue = require('firework').createQueue('https://my-firebase.firebaseio.com/myQueue');
queue.push({ my: 'job' });

Important: The following job property names are reserved:

  • _key
  • _startedAt
  • _succeededAt
  • _failedAt
  • _error

Processing Jobs

The easiest way to start processing the jobs on a Firework queue is to use the firework command:

$ firework create-worker.js -w 5

The -w argument specifies the number of workers to use. When a worker has an unrecoverable error it is removed from the worker pool and replaced with a new one.

The create-worker.js module that you pass to firework should export a function that is used to create new workers. To process jobs from the queue we pushed onto in the Creating Jobs section above, our create-worker.js file could look something like this:

var Firework = require('firework');
var queue = Firework.createQueue('https://my-firebase.firebaseio.com/myQueue');

module.exports = function () {
  return Firework.createWorker(queue, function (job, callback) {
    // process the given job.

    // call the callback when you're done, optionally with
    // any error that was encountered while doing the work.
    callback(error);
  });
};

When Firework is done processing a job it stores the job along with some metadata in the startedJobs child location of your queue. Thus, pendingJobs contains a list of all jobs that still need to be done and startedJobs contains a list of all jobs that you have attempted.

Retrying Failed Jobs

If a job fails, it will have _failedAt and _error properties. You can use the _error property to determine the reason of the failure. Once you've fixed the problem, you can retry all jobs that failed using:

queue.retryFailedJobs();

Installation

Using npm:

$ npm install firework

Issues

Please file issues on the issue tracker on GitHub.

Tests

To run the tests in node:

$ npm install
$ npm test

To run the tests in Chrome:

$ npm install
$ npm run test-browser

License

MIT