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

@babelqueue/pulsar

v1.0.0

Published

Apache Pulsar adapter for BabelQueue — canonical-envelope publisher and a URN-routed consumer.

Readme

@babelqueue/pulsar

Apache Pulsar adapter for BabelQueue — a canonical-envelope publisher and a URN-routed consumer over pulsar-client, on @babelqueue/core. Implements §5 of the broker-bindings contract, so a Pulsar-based Node service speaks the same wire contract as the .NET, Java, Python and Go SDKs.

Install

npm i @babelqueue/pulsar pulsar-client

pulsar-client is an optional peer — you provide the producer/consumer (a Producer / Consumer from pulsar-client satisfies the adapter structurally).

Use

import Pulsar from "pulsar-client";
import { PulsarPublisher, PulsarConsumer } from "@babelqueue/pulsar";

const client = new Pulsar.Client({ serviceUrl: "pulsar://localhost:6650" });

// produce
const producer = await client.createProducer({ topic: "orders" });
const id = await new PulsarPublisher(producer)
  .publish("urn:babel:orders:created", { order_id: 1042 });

// consume (Shared subscription)
const sub = await client.subscribe({
  topic: "orders",
  subscription: "babelqueue",
  subscriptionType: "Shared",
});
const consumer = new PulsarConsumer(
  sub,
  {
    "urn:babel:orders:created": async (env, message) => {
      console.log(env.data.order_id, env.trace_id, env.attempts);
    },
  },
  { onError: (err) => console.error(err) },
);
await consumer.run();

Delayed delivery: publish(urn, data, { delayMs: 300000 }) → native deliverAfter. The consumer routes purely on the bq-job property.

Contract mapping (§5)

| Envelope | Apache Pulsar | | :--- | :--- | | body | message payload (byte-identical across SDKs) | | job (URN) | property bq-job (consumer routes on this) | | trace_id | property bq-trace-id | | meta.id | property bq-message-id | | meta.schema_version | property bq-schema-version | | meta.lang | property bq-source-lang | | meta.created_at | publish time (mirror; body authoritative) | | attempts | property bq-attempts (authoritative), cross-checked against getRedeliveryCount() | | reserve / ack / retry | acknowledge / negativeAcknowledge |

Pulsar properties are string→string, so bq-attempts carries the contract attempts and is authoritative. The consumer reconciles to max(bq-attempts, getRedeliveryCount()): getRedeliveryCount() is 0-based (0 on first delivery) so it maps directly with no −1, and the max never lowers a higher body count — so a republish-driven retry and a native redelivery both converge on the same number. A throwing handler negativeAcknowledges, so the broker redelivers (at-least-once). The poll loop never stops on a bad message — observe via onError / onUnknownUrn. The envelope is unchanged (schema_version stays 1); Pulsar is purely additive.

The producer/consumer are injected, so the unit tests use fakes — no Pulsar, no broker. Dual ESM + CJS.

License

MIT