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

@edd-kernel/provider-rabbitmq

v0.2.0-alpha.1

Published

RabbitMQ EDD Kernel provider.

Readme

@edd-kernel/provider-rabbitmq

RabbitMQ provider for EDD Kernel.

This package belongs to the EDD Kernel provider layer. It owns only the RabbitMQ transport mapping for the shared @edd-kernel/contracts client contract.

Repository: brunnofoggia/edd-kernel-js

Install

npm install @edd-kernel/contracts @edd-kernel/provider-rabbitmq

For provider-name based client creation, install @edd-kernel/factory in place of the contract. It brings the contract and re-exports it:

npm install @edd-kernel/factory @edd-kernel/provider-rabbitmq

Usage

import { createRabbitMqClient } from '@edd-kernel/provider-rabbitmq';

const client = createRabbitMqClient(
    { createIfNotExists: true },
    {
        host: 'localhost',
        port: 5672,
        username: 'guest',
        password: 'guest',
    },
);

await client.send({ queueName: 'jobs' }, { type: 'UserCreated', payload: { id: '1' } });

await client.consume({ queueName: 'jobs' }, async (event, context) => {
    console.log(event);
    await context.ack();
});

Each part goes to amqplib as a field of its own, so a password or a virtual host carrying @, / or : is written as it is — no URL is assembled, and nothing needs to be percent-encoded. A URL is accepted too, and wins over the parts when both are given:

const client = createRabbitMqClient(
    { createIfNotExists: true },
    { url: 'amqp://guest:guest@localhost:5672' },
);

You can also create this provider through @edd-kernel/factory:

import { EddProviderName, createEddClient } from '@edd-kernel/factory';

const client = await createEddClient({
    providerName: EddProviderName.RabbitMq,
    createIfNotExists: true,
    options: {
        host: 'localhost',
        port: 5672,
        username: 'guest',
        password: 'guest',
    },
});

The package also exports RabbitMqEddClient for direct construction and inheritance. Its static provider identity is rabbitmq.

Addressing

| Type | Address | Meaning | | --------------------- | ---------------- | ---------------------------------------------------------- | | RabbitMqEventTarget | { queueName } | A logical name, joined with env, project and prefix. | | RabbitMqEventTarget | { routingKey } | A routing key written in full, used as it is. | | RabbitMqEventQueue | { queueName } | The queue to consume, scoped the same way. |

Any other address is refused by the compiler, and at runtime with EddKernelConfigurationError.

Messages go through the default exchange. A queueName is published with the routing key routingKeyByName gives for it, or with the name itself. durable and queueArguments apply to every queue the provider creates; createQueue overrides them field by field.

Provider Options

  • connection: custom RabbitMQ connection-like object for tests or adapters.
  • channel: custom RabbitMQ channel-like object for tests or adapters.
  • url: AMQP URL or amqplib connection options. When provided, it takes priority over every part below, which are then neither read nor checked. An empty or blank string counts as not provided.
  • host: RabbitMQ host used when url is not provided. Defaults to localhost.
  • port: RabbitMQ port used when url is not provided. Defaults to 5672, or 5671 when scheme is amqps.
  • username: RabbitMQ username used when url is not provided. Defaults to guest.
  • password: RabbitMQ password used when url is not provided. Defaults to guest.
  • virtualHost: AMQP virtual host used when url is not provided. Defaults to /.
  • scheme: amqp, or amqps for AMQP over TLS, used when url is not provided. Defaults to amqp; any other value throws EddKernelConfigurationError.
  • clientOptions: socket options passed to amqplib when the provider connects, whether from the parts or from url — clientProperties included.
  • publishOptions: options passed to sendToQueue.
  • durable: default queue durability when createIfNotExists asserts a queue. Defaults to true.
  • queueArguments: default queue arguments, likewise. Queue metadata overrides both per queue.
  • routingKeyByName: physical routing keys keyed by logical target name.
  • pollIntervalMs: delay between empty polling cycles.
  • nackRequeue: whether nack() requeues messages.

Acknowledgement

This provider uses manual acknowledgements only. autoAck: true means the provider calls the manual ack operation when a message is received; it does not enable RabbitMQ native no-ack delivery.

The provider uses finite channel.get polling for the base consume behavior so multi-queue consumers can rotate between queues without leaving all broker consumers active forever.

Runtime polling failures are logged and retried after pollIntervalMs. Stopping a consumer waits for active handlers, and closing the client stops and drains all consumers before releasing transport resources. Only connections and channels created internally by the kernel are closed; injected resources remain application-owned. Both operations are idempotent.