v3.3.3

Fixed

• Starting a queue overwrote the redis keyspace-notification configuration.
  notify-keyspace-events is a server-global setting, and the watcher owner set
  it to the literal Ex on every connection establishment. Any other flag —
  enabled by an operator through a config file or by other code sharing the same
  redis — was silently dropped, breaking every consumer that relied on it, and
  coming back after each reconnect.

  The current value is now read first, only the missing E/x flags are
  appended, and CONFIG SET is skipped entirely when the configuration already
  suffices. A is recognised as covering x, so a server on AK only gains
  E. When CONFIG is unavailable (e.g. AWS ElastiCache) the read fails and
  the configuration is left untouched — enable notify-keyspace-events out of
  band there, as before.

About

@imqueue/core is the transport layer of the @imqueue framework: a fast JSON message queue over Redis for inter-service communication in Node.js & TypeScript microservices. No-poll delivery (blocking queue ops, zero idle CPU), optional safe delivery, delayed messages, and horizontal scale via competing consumers. Delivery is at-least-once — handlers should be idempotent.

• Docs: https://imqueue.org/
• Guide for AI assistants / LLMs: https://imqueue.org/llms.txt
• Commercial license & support: https://imqueue.com/
• npm i @imqueue/core