v0.1.4

Turn on noUnusedLocals/noUnusedParameters

Isolate a subscriber handler that throws synchronously

Promise.resolve(handler(...)) calls the handler before the promise exists, so
a synchronous throw never reached the .catch: it unwound the dispatch loop and
escaped into the Redis client's own callback, and every later handler on the
channel was skipped. The existing test only covered an async rejection.

Release 0.1.4

Report a subscriber handler that rejects

A message handler is an event callback: nobody awaits it, so a rejection had
nowhere to go. Depending on the runtime that is an unhandledRejection warning
or a process that exits, and either way the failure never reached the logger
that exists for exactly this.

It is reported the way a connection failure is, and the other handlers on the
channel still run.

---

Changes since v0.1.3.