Releases: enisdenjo/graphql-ws
Releases · enisdenjo/graphql-ws
v4.1.6
4.1.6 (2021-02-18)
Bug Fixes
v4.1.5
4.1.5 (2021-02-12)
Bug Fixes
- Main entrypoint in
exports
is just "."
(8f70b02)
v4.1.4
4.1.4 (2021-02-12)
Bug Fixes
- Define entry points through the
exports
field and use .mjs
suffixed ESM imports (#110) (4196238)
v4.1.3
4.1.3 (2021-02-08)
Bug Fixes
- client: Should emit
closed
event when disposing (5800de8), closes #108
- client: Shouldn’t send the
Complete
message if socket is not open (cd12024)
v4.1.2
4.1.2 (2021-01-24)
Bug Fixes
v4.1.1
4.1.1 (2021-01-19)
Bug Fixes
- client: Export relevant elements from the browser bundle (b106dbe), closes #97
- client: Wait for server acknowledgement indefinitely (a4bd602), closes #98
v4.1.0
4.1.0 (2021-01-13)
Bug Fixes
- server:
onDisconnect
is called exclusively if the connection is acknowledged (33ed5f2)
Features
- server: Add
onClose
callback for closures at any point in time (dd0d4fa)
v4.0.0
4.0.0 (2021-01-13)
Bug Fixes
- server: Client can complete/cancel any operation (0ad1c4c)
- server: Enforce ID uniqueness across all operations and during the whole subscription life (#96) (65d1bfa)
Features
- server: Add
onDisconnect
callback (#94) (2a61268)
- server: Log a warning for unsupported subprotocols (88a12ef), closes #92
BREAKING CHANGES
- server: The return function of
server.opened
(closed
) now requires the close event code and reason for reporting to the onDisconnect
callback.
- server: The
Context.subscriptions
record value can be either an AsyncIterator
or a Promise
.
v3.2.0
3.2.0 (2020-12-17)
Features
v3.1.0
3.1.0 (2020-12-11)
Bug Fixes
- client: Time retries and socket change waits (7c707db), closes #85
Features
- client:
onNonLazyError
allows you to catch errors reported in non-lazy mode (cd1e7df)