| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-03-26 | 1.1 kB | |
| v6.0.8 source code.tar.gz | 2026-03-26 | 1.2 MB | |
| v6.0.8 source code.zip | 2026-03-26 | 1.3 MB | |
| Totals: 3 Items | 2.5 MB | 3 | |
Patch Changes
-
#667
fc03004Thanks @endigma! - Fix the server sending aCompletemessage after anErrormessage for subscriptions.Previously, when a subscription's async iterable threw an error, the server would send:
{"id":"1","type":"error","payload":[{"message":"..."}]} {"id":"1","type":"complete"}Per the protocol spec:
Error: This message terminates the operation and no further messages will be sent.
Complete (Server → Client): If the server dispatched the
Errormessage relative to the originalSubscribemessage, noCompletemessage will be emitted.The server now correctly sends only the
Errormessage:{"id":"1","type":"error","payload":[{"message":"..."}]}Clients that correctly follow the spec should be unaffected, as they are expected to ignore messages for operations they consider already completed.