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 🙏

© 2026 – Pkg Stats / Ryan Hefner

joba

v0.5.0

Published

Simple job (task) scheduler (manager).

Readme

joba

Simple job (task) scheduler (manager).

Installation

npm install joba --save

Depending on your choice you should also install bus and persistence dependencies (for example, joba-worque, joba-pg).

Example

Task manager module.

var Joba = require('joba');

var manager = new Joba({
	persistence: {
		name: 'pg',
		connection: {
			uri: 'postgresql://user:password@server/db',
			table: 'tasks'
		}
	},
	bus: {
		name: 'worque',
		connection: {
			host: 'server',
			login: 'user',
			password: 'password'
		}
	}
});

module.exports = manager;

Scheduler app.

var manager = require('./manager');

manager.schedule('* */2 * * *', 'scan web');

Worker app.

var manager = require('./manager');

manager.handle('scan web', scanWeb, true);

function scanWeb () {
	var profitPromise;
	// do something
	return profitPromise;
}

It's recommended to split your task handling process into 2 parts: scheduling and processing and run them into separate applications. It will allow you to restart worker app on failure without loosing the schedule or task being processed while failure has happened.

API

Joba(options)

Constructs manager instance. Accepts 2 options: bus and persistence configuration (see example).

schedule(cronTime, name[, params])

Schedules task execution.

start(name[, params])

Starts immediate task execution.

handle(name, handler[, exitOnFailure][, logParams])

Deprecated (use overload with options as last param).

Specifies task handler. If exitOnFailure is true, then app will exit with code 75 (temporary failure), allowing you to implement restart-on-error management policy for worker app. If logParams is true then params will be saved in the corresponding work log record, if logParams is omitted, then logging will happen only on error, otherwise (if logParams === false) no logging will happen at all.

handle(name, handler[, options])

Specifies task handler.

Options:

name | purpose --- | --- exitOnFailure | if true, then app will exit with code 75 (temporary failure), allowing you to implement restart-on-error management policy for worker app logParams | if true then params will be saved in the corresponding work log record, if omitted, then logging will happen only on error, otherwise (if false) no logging will happen at all concurrency | maximal number of tasks handled simultaneously

pipe(source, destination)

Passes output of one task to input(s) of another task(s).

If destination is string:

source -> destination

otherwise, if destination is object and destination.opcode is map:

source[0] -> destination.names[0]
source[1] -> destination.names[0]
source[2] -> destination.names[0]
...

and if destination.opcode is spread:

source[0] -> destination.names[0]
source[1] -> destination.names[1]
source[2] -> destination.names[2]
...

License

BSD