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

bentools-caduceus

v1.0.0

Published

A lightweight TypeScript library for Mercure real-time updates integration with API Platform / Hydra resources.

Downloads

12

Readme

Caduceus

npm License

Caduceus is a TypeScript library that simplifies real-time data synchronization between your client and server using the Mercure protocol. It provides an elegant way to subscribe to updates on API resources and keep your client-side data in sync with server changes.

Overview

Caduceus consists of two main components:

  1. Mercure - A client for the Mercure protocol that handles the low-level communication with a Mercure hub.
  2. HydraSynchronizer - A higher-level abstraction designed to synchronize Hydra/JSON-LD resources with real-time updates from a Mercure hub.

Core Features

  • 🔄 Real-time data synchronization
  • 🧠 Automatic resource management
  • 🎯 Topic-based subscriptions
  • 🔌 Flexible event handling
  • 🛠️ Customizable configuration options

Usage

Basic Example

import { Mercure, type MercureMessageEvent } from 'bentools-caduceus';

// Create a Mercure client
const mercure = new Mercure('https://example.com/.well-known/mercure');

// Subscribe to specific topics
mercure.subscribe(['/api/books/1', '/api/books/2']);

// Add an event listener
mercure.on('message', async (event: MercureMessageEvent) => {
  const data = await event.json();
  console.log('Received update:', data);
});

// Connect to the Mercure hub
mercure.connect();

// Later, you can unsubscribe from topics
mercure.unsubscribe('/api/books/2');

HydraSynchronizer

If your back-end is built using Hydra (for example with API-Platform), you can use the HydraSynchronizer class to simplify resource synchronization:

import { HydraSynchronizer } from 'bentools-caduceus';

// Create a synchronizer connected to your Mercure hub
const synchronizer = new HydraSynchronizer('https://example.com/.well-known/mercure');

// A resource with an @id property (in Hydra/JSON-LD format)
const resource = {
  '@id': '/api/books/1',
  title: 'The Great Gatsby',
  author: 'F. Scott Fitzgerald'
};

// Start synchronizing the resource
synchronizer.sync(resource);

// The resource object will now be automatically updated
// whenever changes are published to the Mercure hub

[!IMPORTANT]
By default, Caduceus uses the @id property of the resource to determine the topic for Mercure subscriptions. Synchronizing too many resources at once may lead to performance issues. Consider using URI templates or a wildcard topic to reduce the number of subscriptions.

synchronizer.sync(resource, '/api/books/{id}');
// or
synchronizer.sync(resource, '*');

Advanced Usage

Custom Event Handling

import { HydraSynchronizer } from 'bentools-caduceus';

const synchronizer = new HydraSynchronizer('https://example.com/.well-known/mercure');

const book = {
  '@id': '/api/books/1',
  title: 'The Great Gatsby',
  author: 'F. Scott Fitzgerald'
};

// Start synchronizing
synchronizer.sync(book);

// Add custom event handlers
synchronizer.onUpdate(book, (updatedData, event) => {
  console.log('That book was updated:', updatedData);
  // You could trigger UI updates or other side effects here
})

// Listen to deletions (see "Deletion events" below)
synchronizer.onDelete(book, (deletedData, event) => {
  console.log('That book was deleted (or replaced by a minimal @-only payload):', deletedData)
})

Custom Configuration

Both Mercure and HydraSynchronizer accept configuration options:

import { HydraSynchronizer, DefaultEventSourceFactory } from 'bentools-caduceus';

const synchronizer = new HydraSynchronizer('https://example.com/.well-known/mercure', {
  // Custom event source factory
  eventSourceFactory: new DefaultEventSourceFactory(),
  
  // Custom last event ID (for resuming connections)
  lastEventId: 'event-id-123',
  
  // Custom resource listener (signature: (resource, isDeletion) => (data, event) => void)
  resourceListener: (resource, isDeletion) => (data) => {
    if (isDeletion) {
      // Example: mark resource as deleted in UI state
      ;(resource as any).deleted = true
      return
    }
    console.log(`Resource ${resource['@id']} updated`)
    Object.assign(resource, data)
  },
  
  // Custom subscribe options
  subscribeOptions: {
    append: false, // Replace rather than append topics
  },
  
  // Custom event dispatcher (signature: (mercure, updateListeners) => void)
  handler: (mercure, listeners) => {
    mercure.on('message', async (event) => {
      // Custom message handling logic
      const data = await event.json();
      // ...
    });
  },
});

Deletion events

Hydra resources deletions are detected when an event payload contains only JSON-LD metadata keys (those starting with @). When such a payload is received, HydraSynchronizer:

  • routes the event to onDelete listeners for the matching @id, and
  • calls your resourceListener(resource, true) to let you update local state accordingly.

For regular updates (payload includes non-@ keys), the event is routed to onUpdate listeners and resourceListener(resource, false).

API Reference

Mercure

The Mercure class provides a low-level client for a Mercure hub:

Constructor

constructor(hub: string | URL, options?: Partial<MercureOptions>)
  • hub: URL of the Mercure hub
  • options: Configuration options
    • eventSourceFactory: Factory for creating EventSource instances
    • lastEventId: ID of the last event received (for resuming)

Methods

  • subscribe(topic: Topic | Topic[], options?: Partial<SubscribeOptions>): void - Subscribe to one or more topics
  • unsubscribe(topic: Topic | Topic[]): void - Unsubscribe from one or more topics
  • on(type: string, listener: Listener): void - Add an event listener
  • connect(): EventSourceInterface - Connect to the Mercure hub

Authorization Factories

CookieBasedAuthorization

An EventSourceFactory implementation that uses the mercureAuthorization cookie for authorization when connecting to a Mercure hub.

import { CookieBasedAuthorization, Mercure } from 'bentools-caduceus'

const mercure = new Mercure('https://example.com/.well-known/mercure', {
  eventSourceFactory: new CookieBasedAuthorization(),
});

QueryParamAuthorization

An EventSourceFactory implementation that adds an authorization token as a query parameter when connecting to a Mercure hub.

import { QueryParamAuthorization, Mercure } from 'bentools-caduceus'

const token = 'your-jwt-token';
const mercure = new Mercure('https://example.com/.well-known/mercure', {
  eventSourceFactory: new QueryParamAuthorization(token),
});

HydraSynchronizer

The HydraSynchronizer class provides a higher-level abstraction for synchronizing resources:

Constructor

constructor(hub: string | URL, options?: Partial<HydraSynchronizerOptions>)
  • hub: URL of the Mercure hub
  • options: Configuration options
    • resourceListener(resource: ApiResource, isDeletion: boolean): Listener — factory creating a per-resource listener used by sync()
    • subscribeOptions: Options for subscribing to topics (default append: true)
    • handler(mercure: Mercure, listeners: Map<string, Listener[]>): void — installs routing of Mercure events (default handler provided)
    • plus all options from MercureOptions

Methods

  • sync(resource: ApiResource, topic?: string, subscribeOptions?: Partial<SubscribeOptions>) - Start synchronizing a resource (topic defaults to the resource @id)
  • onUpdate(resource: ApiResource, callback: Listener) - Add an update listener for a specific resource
  • onDelete(resource: ApiResource, callback: Listener) - Add a delete listener for a specific resource
  • unsync(resource: ApiResource) - Stop synchronizing a resource

License

MIT License