Releases: websockets/ws
Releases · websockets/ws
7.4.1
Bug fixes
Added a workaround for a double 'error'
event bug in Node.js < 13 which
caused an uncaught error during the WebSocket handshake (38d6ab3 ).
7.4.0
Features
The callback of WebSocketServer.prototype.handleUpgrade()
now takes the
client HTTP GET request as second argument (7d39f19 ).
Bug fixes
Read-only properties are now read-only (eabed8f ).
The CONNECTING
, OPEN
, CLOSING
, CLOSED
, binaryType
, bufferedAmount
,
extensions
, onclose
, onerror
, onmessage
, onopen
, protocol
,
readyState
, and url
properties are now enumerable (2069e68 ).
7.3.0
Features
WebSocket.prototype.addEventListener()
now supports the once
option (#1754 ).
7.2.5
Bug fixes
Fixed compatibility with Node.js master (651d662 ).
7.2.3
Bug fixes
WebSocket#{p{i,o}ng,close}()
now thow an error if the data to send is too
large to fit in a control frame (e54f08d ).
7.2.2
Bug fixes
Fixed an issue where calling webSocketStream.end()
could cause the process
to crash (9535702 ).
The connection is now closed if a non-masked frame is received on the server
or a masked frame is received on the client (#1681 ).
The status code 1014 is now allowed to be used (#1682 ).
7.2.1
Bug fixes
Added bufferutil
and utf-8-validate
as peer dependencies (#1626 ).
7.2.0
Features
Added ability to specify the readableObjectMode
option when using
WebSocket.createWebSocketStream()
(#1647 ).
You can’t perform that action at this time.