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

@amqp-contract/worker

v0.10.0

Published

Worker utilities for consuming messages using amqp-contract

Readme

@amqp-contract/worker

Type-safe AMQP worker for consuming messages using amqp-contract with standard async/await error handling.

CI npm version npm downloads TypeScript License: MIT

📖 Full documentation →

Installation

pnpm add @amqp-contract/worker

Features

  • Type-safe message consumption — Handlers are fully typed based on your contract
  • Automatic validation — Messages are validated before reaching your handlers
  • Automatic retry with exponential backoff — Built-in retry mechanism using RabbitMQ TTL+DLX pattern
  • Prefetch configuration — Control message flow with per-consumer prefetch settings
  • Batch processing — Process multiple messages at once for better throughput
  • Automatic reconnection — Built-in connection management with failover support

Usage

Basic Usage

import { TypedAmqpWorker } from "@amqp-contract/worker";
import type { Logger } from "@amqp-contract/core";
import { contract } from "./contract";

// Optional: Create a logger implementation
const logger: Logger = {
  debug: (message, context) => console.debug(message, context),
  info: (message, context) => console.info(message, context),
  warn: (message, context) => console.warn(message, context),
  error: (message, context) => console.error(message, context),
};

// Create worker from contract with handlers (automatically connects and starts consuming)
const worker = await TypedAmqpWorker.create({
  contract,
  handlers: {
    processOrder: async (message) => {
      console.log("Processing order:", message.orderId);

      // Your business logic here
      await processPayment(message);
      await updateInventory(message);

      // If an exception is thrown, the message is automatically requeued
    },
  },
  urls: ["amqp://localhost"],
  logger, // Optional: logs message consumption and errors
});

// Worker is already consuming messages

// Clean up when needed
// await worker.close();

Advanced Features

For advanced features like prefetch configuration, batch processing, and automatic retry with exponential backoff, see the Worker Usage Guide.

Retry with Exponential Backoff

Enable automatic retry for failed messages:

const worker = await TypedAmqpWorker.create({
  contract,
  handlers: {
    processOrder: async (message) => {
      // If this throws, message is automatically retried with exponential backoff
      await processPayment(message);
    },
  },
  urls: ["amqp://localhost"],
  retry: {
    maxRetries: 3, // Retry up to 3 times
    initialDelayMs: 1000, // Start with 1 second delay
    maxDelayMs: 30000, // Max 30 seconds between retries
    backoffMultiplier: 2, // Double the delay each time
    jitter: true, // Add randomness to prevent thundering herd
  },
});

The retry mechanism uses RabbitMQ's native TTL and Dead Letter Exchange pattern, so it doesn't block the consumer during retry delays. See the Error Handling and Retry section in the guide for complete details.

Defining Handlers Externally

You can define handlers outside of the worker creation using defineHandler and defineHandlers for better code organization. See the Worker API documentation for details.

Error Handling

Worker handlers use standard Promise-based async/await pattern:

handlers: {
  processOrder: async (message) => {
    // Standard async/await - no Result wrapping needed
    try {
      await process(message);
      // Message acknowledged automatically on success
    } catch (error) {
      // Exception automatically caught by worker
      // With retry configured: message is retried with exponential backoff
      // Without retry: message is immediately requeued
      throw error;
    }
  };
}

Error Types:

Worker defines error classes:

  • TechnicalError - Runtime failures (parsing, processing)
  • MessageValidationError - Message fails schema validation
  • RetryableError - Optional error class for explicit retry signaling (all errors are retryable by default when retry is configured)

Handlers don't need to use these error classes - just throw standard exceptions. The worker handles retry automatically based on your configuration.

API

For complete API documentation, see the Worker API Reference.

Documentation

📖 Read the full documentation →

License

MIT