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

egg-bull-new

v2.0.1

Published

bull plugin for egg framework

Readme

egg-bull-new

NPM version CI

Bull (Redis) queue plugin for Egg.

Compatibility

Starting from 2.x this plugin targets Egg 4:

| Dependency | Version | | --- | --- | | egg | ^4.2.0 (peer dependency) | | node | >= 22.18.0 |

The plugin is registered as an Egg 4 boot hook: the bull singleton is created during didLoad and app/queue/** is loaded during willReady, so every queue is available before app.ready() resolves.

For Egg 3 use [email protected].

Install

$ npm i egg-bull-new --save

Usage

// {app_root}/config/plugin.ts
import { EggPlugin } from 'egg';

const plugin: EggPlugin = {
  bull: {
    enable: true,
    package: 'egg-bull-new',
  },
};

export default plugin;

Configuration

Single queue

// {app_root}/config/config.default.js
exports.bull = {
  client: {
    name: 'queue',
    redis: {
      host: 'localhost',
      port: 6379,
      db: 0,
    },
  },
};

Multiple queue (recommended)

exports.bull = {
  clients: {
    q1: { name: 'q1' },
    q2: { name: 'q2' },
  },
  default: {
    redis: {
      host: 'localhost',
      port: 6379,
      db: 0,
    },
  },
};

default is merged into every client, so shared redis/job options only need to be written once. Note that the merge is shallow: a defaultJobOptions defined on a client replaces the whole default.defaultJobOptions object.

The plugin also exposes its own config.queue knobs — delegate (default queue), baseDir (default queue), app (default true) and agent (default false) — which control where app/queue/** is loaded from and whether the queues are created in the application worker or the agent worker. See config/config.default.js for more detail.

Example

// {app_root}/app/queue/video.js
module.exports = app => {
  const queue = app.bull.get('videoQueue');

  queue.process((job, done) => {
    job.progress(42);
    done();
  });

  return queue;
};

// {app_root}/app/controller/video.js
async function (ctx) {
  await ctx.queue.video.add({ video: 'http://example.com/video1.mov' });
};

Every file under app/queue/** is loaded onto app.queue and ctx.queue, keyed by file name. Queues that are not registered in config.bull.clients (such as a queue created with new app.Queue(name, opts)) are supported as well.

For Bull's api read Reference for more details.

Test

$ npm test

The tests need a local Redis listening on 127.0.0.1:6379 with the password foobared:

$ docker run -d --name redis -p 6379:6379 redis:7 redis-server --requirepass foobared

License

MIT