Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.1.1
->^3.0.0
By merging this PR, the issue #11 will be automatically resolved and closed:
Release Notes
websockets/ws (ws)
v3.3.1
Compare Source
Bug fixes
c4fe466
).A specially crafted value of the
Sec-WebSocket-Extensions
header thatused
Object.prototype
property names as extension or parameter namescould be used to make a ws server crash.
The vulnerability has been privately reported by Nick Starke and
Ryan Knell of Sonatype Security Research and promptly fixed. Please
update now!
v3.3.0
Compare Source
Features
ecdhCurve
option (#1228).v3.2.0
Compare Source
Features
v3.1.0
Compare Source
Features
Bug fixes
CloseEvent#wasClean
was incorrectly set tofalse
forclose codes in the 3000-4999 range (#1146).
v3.0.0
Compare Source
Breaking changes
upgradeReq
property (#1099).flags
argument from the'message'
,'ping'
, and'pong'
events (#1101).
(#1107).
v2.3.1
Compare Source
Bug fixes
WebSocket.prototype.close()
from workingproperly when called from a listener of the
headers
event (732aaf0
).v2.3.0
Compare Source
Features
WebSocket
client now emits aheaders
event (#1082).v2.2.3
Compare Source
Notable changes
Bug fixes
options
argument to be reassigned whenprotocols
wasnull
(20bd7c7
).v2.2.2
Compare Source
Bug fixes
v2.2.1
Compare Source
Bug fixes
WebSocket.prototype.terminate()
now closes the connection immediately evenif the other peer fails to work properly (#1033).
v2.2.0
Compare Source
Features
binaryType
attribute (#1018).Bug fixes
5edb460
).v2.1.0
Compare Source
Features
060b275
).Bug fixes
synchronously on the socket while parsing data (
6695bd4
).v2.0.3
Compare Source
Bug fixes
thousands of frames (#992).
f043b52
).v2.0.2
Compare Source
Notable changes
bufferutil@2
andutf-8-validate@3
(466e210
).v2.0.1
Compare Source
Bug fixes
d856dcb
).v2.0.0
Compare Source
Breaking changes
new
operator is now required to create all instances as we moved to ES6classes.
clients
property of theWebSocketServer
is no longer anArray
but aSet
and is only set if theclientTracking
option is truthy (#806).41e7cae
).WebSocketServer
swhen binding them to the same underlying HTTP/s server (#885).
WebSocket.prototype.stream()
and ability to pass a readable streamto
WebSocket.prototype.send()
(#875).handleProtocols
handler (#890).supports
property fromWebSocket
(#918).WebSocket.createServer()
,WebSocket.createConnection()
, andWebSocket.connect()
factory functions (#926).WebSocket.prototype.ping()
andWebSocket.prototype.pong()
is no longer an options object but a boolean(#951).
WebSocket.prototype.close()
is called before theconnection is established (#956).
The following breaking changes only apply if you required the mentioned classes
directly.
Sender
inheritance fromEventEmitter
(#861).BufferPool
class (73ab370
).extensions
a required argument for theReceiver
constructor (5f53194
).receiver.onbinary
andreceiver.ontext
have been merged intoreceiver.onmessage
(#939).Features
WebSocketServer
(#795).checkServerIdentity
option toWebSocket
(#701).threshold
option for permessage-deflate to only compress messageswhose size is bigger than
threshold
(6b3904b
).shouldHandle
method toWebSocketServer
to see if a request shouldbe accepted or rejected. This method can be overridden by the user if a
custom logic is desired (
6472425
).removeEventListener
method toWebSocket
(078e96a
).family
option toWebSocket
(#962).Bug fixes
handled (#744).
error
events are now emitted with a properError
instance (#789).b58f688
).validation failed (#534).
fin
option ofWebSocket.prototype.send()
wasunconditionally set to
true
(ea50be7
).being correctly calculated (
545635d
).zlib.flush()
was called with a wrong flush level(#733).
WebSocketServer.prototype.close()
is now invoked when theclose
event is emitted by the underlying HTTP/s server (#892).with default settings (
dcdc652
).connection
event was emitted even if the clientclosed the connection during the handshake process (
04530ad
).crypto.randomBytes()
instead ofMath.random()
(7253f06
).discarded (#945).
clients
set (#955).
WebSocket.prototype.close()
now works as expected if called on the clientbefore the connection is established (#956).
WebSocket.prototype.send()
no longer mutates the options object (#968).bufferedAmount
getter now takes into account the data queued in thesender (#971).
v1.1.5
Compare Source
Bug fixes
f8fdcd4
).v1.1.4
Compare Source
Notable changes
fac50ac
).v1.1.3
Compare Source
Notable changes
bufferutil@>1
andutf-8-validate@>2
(b4cf110
).v1.1.2
Compare Source
Bug fixes
crypto.randomBytes()
instead ofMath.random()
(#994).c1f3b21
).