blog · release

bunqueue v2.8.9

Ships 3 additions. Remote failure → the job fails locally (retry with backoff → local DLQ): persist the source queue to survive an uplink outage while its process or volume survives; retryDlq() re-enqueues when connectivity returns.

egeominotti

To install bunqueue v2.8.9

bun add bunqueue@2.8.9

npm install bunqueue@2.8.9

To upgrade bunqueue

bun add bunqueue@latest

What’s new

queue.forward(), built-in store-and-forward from a local (edge) queue to a remote bunqueue server. The IoT/edge pattern as a one-liner:

const fwd = localQueue.forward({
  to: { host: 'central.example.com', port: 6789, tls: true, token },
  queue: 'ingest', // optional remote name
});

Prebuilt binaries, every release now attaches self-contained executables (no Bun install needed): linux-x64, linux-arm64, darwin-x64, darwin-arm64 + SHA256SUMS. Built for edge gateways (Raspberry Pi 4/5, ARM64 boxes): download, untar, run.

More additions

• Remote failure → the job fails locally (retry with backoff → local DLQ): persist the source queue to survive an uplink outage while its process or volume survives; retryDlq() re-enqueues when connectivity returns.
• Deduped re-forwards: forwarded jobs carry the deterministic remote jobId fwd:<queue>:<localId>, deduped server-side within the custom-id retention window (bounded LRU; remote removeOnComplete evicts the entry, for strict exactly-once across long outages, dedupe downstream).
• Preserves job name, data and priority; optional durable: true for per-job fsync server-side; forwarded/error events.

Thanks to 1 contributor!

• @egeominotti

---

← bunqueue v2.8.8 · Release on GitHub · Commits since v2.8.8 · Full changelog · All posts