A small, testable ESM RabbitMQ client for Node.js.
- Publish JSON messages to exchanges.
- Declare exchanges, queues, and bindings, then consume messages.
- Reuse one connection/channel per process.
- Accept a RabbitMQ URL or environment-based configuration.
- Dependency-inject
amqpliband a logger for deterministic tests. - Acknowledge messages only after the handler completes.
- Reconnect after transient connection/channel failures.
- Expose explicit connection, health-check, status, and close helpers.
- Support TLS options, custom serialization, message properties, backpressure, and failed-message requeue behavior.
- Provide confirmed publishing APIs for durable mail and job delivery.
- Support explicit exchange, queue, and topology operations without breaking the original API.
- Includes TypeScript declarations and structured
RabbitMQErrorerrors.
- Node.js 26 or newer
- A reachable RabbitMQ server for publish/consume operations
npm install @eliware/rabbitmqSet RABBITMQ_URL directly, or set RABBITMQ_HOST, RABBITMQ_USER, RABBITMQ_PASS, and optionally RABBITMQ_VHOST. The generated URL is amqp://user:pass@host/vhost; credentials and the virtual host are URL-encoded. An explicit rabbitUrl in the final options object takes precedence.
For TLS connections, use an amqps:// URL and pass TLS options through tls. Keep certificate contents in environment variables or secret storage; do not commit certificate files or private keys. The examples/tls.mjs example reads RABBITMQ_TLS_CA and RABBITMQ_TLS_REJECT_UNAUTHORIZED.
import rabbitmq from '@eliware/rabbitmq';
await rabbitmq.publish('events', 'topic', { event: 'created' });
await rabbitmq.consume('events', 'topic', async (message) => {
console.log(message);
});publish(queue, type, message, exchangeOptions?, runtimeOptions?) declares the exchange and publishes JSON using queue as both exchange and routing key. consume(queue, type, handler, options?, runtimeOptions?) declares the exchange and queue, binds them, and invokes the handler with parsed JSON. Queues default to durable unless durable: false is explicitly supplied; this avoids deprecated transient non-exclusive queues on newer RabbitMQ versions. Invalid JSON is delivered as text.
Runtime options are { rabbitUrl, amqplibLib, logger, tls, reconnect, reconnectDelay, serialize, deserialize, messageOptions, consumeOptions, requeueOnError }. A logger can provide debug() and error() methods. RabbitMQError identifies connection/configuration failures and exposes an operation field.
import { RabbitMQError, getRabbitUrl } from '@eliware/rabbitmq';
if (!getRabbitUrl()) throw new Error('RabbitMQ configuration is missing');
try {
await rabbitmq.publish('events', 'direct', { ok: true }, {}, { rabbitUrl: process.env.RABBITMQ_URL });
} catch (error) {
if (error instanceof RabbitMQError) console.error(error.operation, error.message);
throw error;
}connect() establishes or reuses the shared connection, isConnected() reports its state, verifyConnection() performs a health check, and close() gracefully closes it. Operations retry once after a connection failure by default; set reconnect: false to disable that behavior. Acknowledge/reject failures during shutdown are safely ignored and logged at debug level. _resetRabbitMQTestState() is retained for test cleanup or deliberate reconnects.
For work that must not be reported successful until RabbitMQ has accepted it, use the confirmed APIs:
await rabbitmq.publishExchange('mail.direct', 'mail.outbound.submit', job, {}, {
messageOptions: { persistent: true, contentType: 'application/json' },
});
await rabbitmq.publishQueue('mailbot', notification, {
messageOptions: { persistent: true, contentType: 'application/json' },
});publishExchange() uses a confirm channel, waits for broker confirmation, and closes only its temporary channel. publishQueue() asserts a durable queue and confirms direct queue delivery. ensureTopology() accepts definitions with type: 'exchange', type: 'queue', or type: 'binding' and declares them idempotently. The original publish() and consume() APIs remain unchanged for existing applications.
Both RABBITMQ_USER/RABBITMQ_PASS and the equivalent RABBITMQ_USERNAME/RABBITMQ_PASSWORD environment names are supported.
Runnable examples are in examples/:
basic-publish.mjsconsume.mjstls.mjsreconnect.mjscustom-serialization.mjsgraceful-shutdown.mjs
Run one with node examples/basic-publish.mjs after configuring the RABBITMQ_* environment variables. Examples use environment variables and close connections during finite operations.
Type declarations are included automatically:
import { consume, publish } from '@eliware/rabbitmq';
await publish('events', 'direct', { hello: 'world' });
await consume('events', 'direct', (message) => console.log(message));Connection and operation failures are surfaced as RabbitMQError with an operation name. Credentials, message contents, URLs containing credentials, and TLS material are not logged. Operations retry once after transient connection failures by default; disable this with reconnect: false when appropriate. Always call close() during shutdown.
npm test
npm run lint
npm run typecheck
npm audit --omit=dev --audit-level=moderate
npm run packTests use @eliware/test, inject amqplib, logging, and runtime configuration, and enforce 100% statements, branches, functions, and lines coverage. A live RabbitMQ server is optional.
Keep RabbitMQ credentials and certificates in environment variables or secret storage. Use TLS options for secure deployments and never log passwords, private keys, credential-bearing URLs, or message payloads.