Releases: websockets/ws
Releases · websockets/ws
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 ).
7.1.2
Bug fixes
Fixed a bug that caused compress jobs to never be marked as complete
(#1618 ).
7.1.1
Bug fixes
An error is now thrown if the WebSocket
server constructor is used
incorrectly (3641266 ).
7.1.0
Features
Added utility to wrap a WebSocket
in a Duplex
stream (#1589 ).
Bug fixes
Reverted "[minor] Remove unneeded if
statement" (dbacf58 , #1591 ).
7.0.1
Bug fixes
Added ability to disable sending the SNI extension (#1587 ).
7.0.0
Breaking changes
Dropped support for Node.js 6 (1e6999b ).
Dropped support for url.Url
instances in the WebSocket
constructor
(692d7b4 ).
The behavior of WebSocket#{p{i,o}ng,send}()
has changed when the
readyState
attribute is not OPEN
(#1532 )
If the readyState attribute is CONNECTING
, an exception is thrown.
If the readyState attribute is CLOSING
or CLOSED
The bufferedAmount
attribute is increased by the length of the data
argument in bytes.
If provided, the callback
function is called with an error.
No exception is thrown even if the callback
function is not provided.
You can’t perform that action at this time.