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

@inventaire/level-jobs

v3.1.1

Published

Job Queue in LevelDB

Readme

level-jobs

Job Queue in LevelDB for Node.js

Build Status

  • Define worker functions
  • Persist work units
  • Work units are retried when failed
  • Define maximum concurrency

Install

$ npm install level-jobs --save

Use

Create a levelup database

import level from 'classic-level'
const db = level('./db')

Import level-jobs

import Jobs from 'level-jobs'

Define a worker function

This function will take care of a work unit.

async function worker(id, payload) {
  await doSomething()
}

This function gets 3 arguments:

  • id uniquely identifies a job to be executed.
  • payload contains everyting worker need to process the job.

If the function throws an error, the work unit is retried.

Wrap the database

const queue = Jobs(db, worker)

This database will be at the mercy and control of level-jobs, don't use it for anything else!

(this database can be a root levelup database or a sublevel)

You can define a maximum concurrency (the default is Infinity):

const maxConcurrency = 2
const queue = Jobs(db, worker, maxConcurrency)

More Options

As an alternative the third argument can be an options object with these defaults:

const options = {
  maxConcurrency: Infinity,
  maxRetries:     10,
  workerTimeout: Infinity,
  batchLength: 1,
  backoff: {
    randomisationFactor: 0,
    initialDelay: 10,
    maxDelay: 300
  }
  // preWorker: async () => {} // No preWorker hook set by default, but you can set one, for instance to wait for worker dependencies without this time being counted in the workerTimeout
}

const queue = Jobs(db, worker, options)

Push work to the queue

const payload = { what: 'ever' }

try {
  const jobId = await queue.push(payload))
} catch (err) {
  console.error('Error pushing work into the queue', err.stack)
}

or in batch:

const payloads = [
  { what: 'ever' },
  { what: 'ever' }
]

try {
  const jobIds = await queue.pushBatch(payloads)
} catch (err) {
  console.error('Error pushing works into the queue', err.stack)
}

or with a custom job id (for instance, to customize works execution order, or use a determistic id to avoid creating duplicate jobs):

const payload = { what: 'ever' }

try {
  const jobId = 'abc123'
  await queue.pushWithCustomJobId(jobId, payload))
} catch (err) {
  console.error('Error pushing work into the queue', err.stack)
}

which can also be done in batch:

const payload = { what: 'ever' }

try {
  const jobs = [
    [ 'abc123', payload ],
    [ 'efg456', payload ],
  ]
  await queue.pushBatchWithCustomJobIds(jobs))
} catch (err) {
  console.error('Error pushing work into the queue', err.stack)
}

Delete pending job

(Only works for jobs that haven't started yet!)

try {
  await queue.del(jobId)
} catch (err) {
  console.error('Error deleting job', err.stack)
}

or in batch:

try {
  await queue.delBatch(jobIds)
} catch (err) {
  console.error('Error deleting jobs', err.stack)
}

Worker batch mode

By default, the worker received one job id and payload at a time, but it's also possible to execute jobs in batches:

async function batchWorker(jobEntries) {
  await doSomething()
}

This function gets a single argument: jobEntries, which is an array of job ids and payloads tuples.

To use a batch worker, the queue batchLength option MUST be above 1. For example:

const queue = Jobs(db, batchWorker, {
  batchLength: 50,
  maxConcurrency: 5,
})

Traverse jobs

queue.pendingStream() emits queued jobs. queue.runningStream() emits currently running jobs.

const stream = queue.pendingStream()
stream.on('data', function (data) {
  const jobId = data.key
  const payload = data.value
  console.log('pending job id: %s, payload: %j', jobId, payload)
})

Events

A queue object emits the following event:

  • drain — when there are no more jobs pending. Also happens on startup after consuming the backlog work units.
  • error - when something goes wrong.
  • retry - when a job is retried because something goes wrong.

Client isolated API

If you simply want a pure queue client that is only able to push jobs into the queue, you can use level-jobs/client like this:

import QueueClient from 'level-jobs/client'

const client = QueueClient(db)

try {
  await client.push(work)
  console.log('pushed')
} catch (err) {
  console.error('pushing failed', err)
}

License

MIT