graphql-ws

6.4.1 · 15 Oct 2026MIT10.6M / weekRepository Homepage npm Atom feed

Your version

6.0.8

26 Mar 2026Where it was published

6.4.1 is the newest release of 6.x.

In short

1 fixed

Release note

Patch Changes

Fix the server sending a Complete message after an Error message 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 Error message relative to the original Subscribe message, no Complete message will be emitted.
The server now correctly sends only the Error message:
```
{"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.