bunqueue v2.8.8
Server, fail fast, client SDK, CLI client.
To install bunqueue v2.8.8
Section titled “To install bunqueue v2.8.8”bun add bunqueue@2.8.8npm install bunqueue@2.8.8To upgrade bunqueue
Section titled “To upgrade bunqueue”bun add bunqueue@latestWhat’s new
Section titled “What’s new”Native TLS termination, no reverse proxy needed. Opt-in and fully backward compatible: without cert/key config, both servers behave exactly as before (plaintext).
MQTT → bunqueue bridge example (examples/mqtt-bridge/), IoT/edge
recipe: MQTT messages become persisted jobs with retries, DLQ and offline
buffering on an edge gateway (embedded SQLite queue), with optional TLS
forwarding to a central server.
Server
Section titled “Server”bunqueue start --tls-cert ./cert.pem --tls-key ./key.pem, or
TLS_CERT_FILE/TLS_KEY_FILE env vars, or server.tlsCertFile/tlsKeyFile
in bunqueue.config.ts. One cert pair covers the TCP server (msgpack
protocol, unchanged) and the HTTP server (https:///wss://).
Fail fast
Section titled “Fail fast”Missing cert/key file or a partial config (cert without key) is a startup error, the server never silently falls back to plaintext.
Client SDK
Section titled “Client SDK”connection.tls on Queue/Worker, true (system CAs),
{ caFile } (private CA / self-signed with full verification), or
{ rejectUnauthorized: false } (dev only). TLS and plaintext pools to the
same host:port are never shared.
CLI client
Section titled “CLI client”--tls, --tls-ca <file>, --tls-no-verify global flags.
More additions
Section titled “More additions”- Pooled TCP clients no longer crash the process on socket-level errors (e.g. a plaintext client hitting a TLS server): the error is observed and pending commands settle through the close/timeout paths.
- New guide: Native TLS.
Thanks to 1 contributor!
Section titled “Thanks to 1 contributor!”← bunqueue v2.8.7 · Release on GitHub · Commits since v2.8.7 · Full changelog · All posts