graphql-ws - npm Package Versions

5.5.3 (2021-10-20)

Bug Fixes

• client: Distinguish client connection closes (ed4d9db)

5.5.2 (2021-10-20)

Bug Fixes

• client: Don't complete after connection error (5f829c3)
• client: Report close error even if Complete message followed (27754b2), closes #245

5.5.1 (2021-10-19)

Bug Fixes

• server: Limit internal server error close message size (8479f76)
• server: Log internal errors to the console (6ddf0d1)
• ws,fastify-websocket: Send only on ready socket (8d13c9e)

5.5.0 (2021-09-08)

Bug Fixes

• Define graphql execution results (a64c91b)
• server: Operation result can be async generator or iterable (b1fb883)

Features

• client: Add connectionAckWaitTimeout option (#228) (35ce054)

5.4.1 (2021-08-26)

Bug Fixes

• Add support for graphql@v16 (ad5aea2)
• Sink's next callback always receives an ExecutionResult (045b402)

5.4.0 (2021-08-21)

Bug Fixes

• client: Specify and fail on fatal internal WebSocket close codes (a720125)
• Use 4406 close code for unsupported subprotocol (1002 is an internal WebSocket close code) (df85281)
• Use 4500 close code for internal server errors (1011 is an internal WebSocket close code) (3c0316d)

Features

• Centralise expected close codes in CloseCode enum (d10a75c)
• server: Add support for ws@v8 (9119153)

5.3.0 (2021-06-23)

Bug Fixes

• client: ConnectionInit payload is absent if connectionParams returns nothing (98f8265)

Features

• client: connectionParams can return undefined (a543187)
• client: Add opened event for when a WebSocket opens (9053224)

5.2.0 (2021-06-21)

Features

• server: Optional onPing and onPong message type listeners (f36066f)

5.1.2 (2021-06-09)

Bug Fixes

• client: Return ping's payload through the response pong (ee6193a)

5.1.1 (2021-06-09)

Bug Fixes

• server: Return ping's payload through the response pong (47730a9), closes #117