fix(deps): update dependency ws to v8 - autoclosed #311
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:
^7.2.3
->^8.0.0
^7.2.3
->^8.0.0
Release Notes
websockets/ws
v8.12.0
Compare Source
Features
utf-8-validate@6
(ff63bba
).Other notable changes
buffer.isUtf8()
][buffer.isUtf8()] is now used instead ofutf-8-validate
if available(
42d79f6
).v8.11.0
Compare Source
Features
WebSocket.prototype.addEventListener()
now supports an event listenerspecified as an object with a
handleEvent()
method. (9ab743a
).Bug fixes
WebSocket.prototype.addEventListener()
now adds an event listener only if itis not already in the list of the event listeners for the specified event type
(
1cec17d
).v8.10.0
Compare Source
Features
211d5d3
).v8.9.0
Compare Source
Features
v8.8.1
Compare Source
Bug fixes
Authorization
andCookie
headers are no longer sent if the originalrequest for the opening handshake is sent to an IPC server and the client is
redirected to another IPC server (
bc8bd34
).v8.8.0
Compare Source
Features
WS_NO_BUFFER_UTIL
andWS_NO_UTF_8_VALIDATE
environmentvariables (
becf237
).v8.7.0
Compare Source
Features
them with a custom HTTP response. (
6e5a5ce
).Bug fixes
Upgrade
header field value in the HTTPresponse is not a case-insensitive match for the value "websocket" (
0fdcc0a
).Authorization
andCookie
headers are no longer sent when following aninsecure redirect (wss: to ws:) to the same host (
d68ba9e
).v8.6.0
Compare Source
Features
v8.5.0
Compare Source
Features
WebSocket
class on the server (#2007).Bug fixes
Authorization
andCookie
headers are nolonger sent if the redirect host is different from the original host (#2013).
v8.4.2
Compare Source
Bug fixes
v8.4.1
Compare Source
Notable changes
websocket.ping()
,websocket.pong()
, andwebsocket.send()
are no longer converted toBuffer
s if the data does not need to be masked (#2000).v8.4.0
Compare Source
Features
v8.3.0
Compare Source
Features
WebSocket
(0a8c7a9
).Bug fixes
using the stream API (
ed2b803
).redirect URL is invalid (#1980).
v8.2.3
Compare Source
Bug fixes
is below the value of the
perMessageDeflate.threshold
option (41ae563
).v8.2.2
Compare Source
Bug fixes
ec9377c
).v8.2.1
Compare Source
Bug fixes
from being closed cleanly (
869c989
).v8.2.0
Compare Source
Features
WebSocket.WebSocket
as an alias forWebSocket
andWebSocket.WebSocketServer
as an alias forWebSocket.Server
to fix nameconsistency and improve interoperability with the ES module wrapper (#1935).
v8.1.0
Compare Source
Features
Bug fixes
6a72da3
).c95e695
).v8.0.0
Compare Source
Breaking changes
The
WebSocket
constructor now throws aSyntaxError
if any of thesubprotocol names are invalid or duplicated (
0aecf0c
).The server now aborts the opening handshake if an invalid
Sec-WebSocket-Protocol
header field value is received (1877dde
).The
protocols
argument ofhandleProtocols
hook is no longer anArray
buta
Set
(1877dde
).The opening handshake is now aborted if the
Sec-WebSocket-Extensions
headerfield value is empty or it begins or ends with a white space (
e814110
).Dropped support for Node.js < 10.0.0 (
552b506
).The
WebSocket
constructor now throws aSyntaxError
if the connection URLcontains a fragment identifier or if the URL's protocol is not one of
'ws:'
,'wss:'
, or'ws+unix:'
(ebea038
).Text messages and close reasons are no longer decoded to strings. They are
passed as
Buffer
s to the listeners of their respective events. The listenersof the
'message'
event now take a boolean argument specifying whether or notthe message is binary (
e173423
).Existing code can be migrated by decoding the buffer explicitly.
The package now uses an ES module wrapper (
78adf5f
).WebSocketServer.prototype.close()
no longer closes existing connections(
df7de57
).Existing code can be migrated by closing the connections manually.
The callback of
WebSocketServer.prototype.close()
is now called with anerror if the server is already closed (
abde9cf
).WebSocket.prototype.addEventListener()
is now a noop if thetype
argumentis not one of
'close'
,'error'
,'message'
, or'open'
(9558ed1
).WebSocket.prototype.removeEventListener()
now only removes listeners addedwith
WebSocket.prototype.addEventListener()
and only one at time (ea95d9c
).The value of the
onclose
,onerror
,onmessage
, andonopen
properties isnow
null
if the respective event handler is not set (6756cf5
).The
OpenEvent
class has been removed (21e6500
).Bug fixes
event listeners added with
WebSocket.prototype.addEventListener()
(
0b21c03
).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.