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

@tulipes/bullmq

v0.1.1

Published

BullMQ queues provider for Tulipes apps: producers in every process, consumers in the worker, behind core's queues capability

Readme

@tulipes/bullmq

The BullMQ queues provider for Tulipes apps. Every module's queues/*.queues.ts runs in every process: producers exist everywhere, processors are registered everywhere, and the worker process turns them into consumers. Core itself no longer installs BullMQ or ioredis; an app without background work declares no provider and never pays for one.

Requires Node 24.x and a core that ships the provider contract with serve/drain hooks. bullmq and ioredis are this package's own dependencies — the app never imports BullMQ, and the provider's connections are never shared with the app's own Redis clients.

Select it

{ "tulipes": { "providers": { "queues": "@tulipes/bullmq" } } }

plus REDIS_URL declared by the app's sys core module and set. A queues/ directory requires the provider automatically; a module that only produces declares "tulipes": { "requires": ["queues"] }. Installing this package without the declaration selects nothing; a REDIS_URL on its own starts nothing.

Use it

// modules/billing/queues/invoices.queues.ts
import type { Ctx } from "@tulipes/core/boot";
import type { QueueRegistry } from "@tulipes/bullmq";

export default function invoiceQueues(ctx: Ctx, queues: QueueRegistry): void {
  queues.define("billing.send-invoice");
  queues.process("billing.send-invoice", async (job) => ({ sent: true }));
}

// anywhere after acquisition
await requireQueues(ctx).add("billing.send-invoice", "send", { invoiceId });

Behavior

  • One ioredis connection per queue and one blocking connection per worker, maxRetriesPerRequest: null; owned by core before the first queue file runs.
  • Worker mode: serve() starts one Worker per registered processor; core refuses a worker that serves nothing.
  • Shutdown: drain() closes workers (finishing active jobs) concurrently with the HTTP drain and module onDrain hooks while producers stay usable — a module's onShutdown may still enqueue; then queues and connections close in reverse provider order, with forced disconnect() under the shared deadline.
  • Queue names use .; duplicates and processors for undefined queues are aggregate boot errors naming the modules.

Versions

0.1.0-rc.1 requires core ^0.10.0-rc.2, the candidate that added the serve/drain hooks; install both with @next. See core's MIGRATING.md.