mq-bridge-pulsar (Node.js)

An Apache Pulsar endpoint for mq-bridge, shipped as a native plugin. The package contains no JavaScript implementation of Pulsar — it loads the compiled Rust endpoint into mq-bridge, so Node.js, Python and Rust all run the same code and the same delivery semantics.

npm install mq-bridge mq-bridge-pulsar

import { Route } from "mq-bridge";
import { register } from "mq-bridge-pulsar";

register(); // call once, before starting routes

const route = Route.fromStr(`
pulsar_to_file:
  input:
    custom:
      name: pulsar
      config:
        url: "pulsar://localhost:6650"
        topic: "persistent://public/default/orders"
        subscription: "order-workers"
        initial_position: earliest
  output:
    file:
      path: "orders.jsonl"
`);
route.start();
route.join(); // block until the route stops

initial_position (optional, input only, latest by default) decides where Pulsar starts a subscription it has to create; earliest is what reading a topic's existing backlog needs. It applies only at creation — see the root README.md for the full rules.

register() returns the endpoint name (pulsar) and is a no-op when called again. mq-bridge selects the current platform's library from this package's prebuilds/ directory using the shared plugin-package convention.

A plugin is native code with the same privileges as the Node process — install it as you would any other native dependency.

Building the package

The packaging command shipped by mq-bridge builds the Rust cdylib and stages it under the current platform tag:

mq-bridge-package-plugin

Run it on each supported target and merge the resulting node/prebuilds/ directories. Then create the single tarball that is published to npm:

mq-bridge-package-plugin --pack --out npm

Building pulsar-rs needs protoc on PATH.