Update dependency socket.io to v4#8
Open
dev-mend-for-github-com[bot] wants to merge 1 commit intomasterfrom
Open
Update dependency socket.io to v4#8dev-mend-for-github-com[bot] wants to merge 1 commit intomasterfrom
dev-mend-for-github-com[bot] wants to merge 1 commit intomasterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^3.1.0→^4.5.2By merging this PR, the below vulnerabilities will be automatically resolved:
Release Notes
socketio/socket.io (socket.io)
v4.5.2Compare Source
Bug Fixes
Links:
~6.2.0~8.2.3v4.5.1Compare Source
Bug Fixes
Links:
~6.2.0~8.2.3v4.5.0Compare Source
Bug Fixes
Features
This is similar to
onAny(), but for outgoing packets.Syntax:
Syntax:
So that clients in HTTP long-polling can decide how many packets they have to send to stay under the maxHttpBufferSize
value.
This is a backward compatible change which should not mandate a new major revision of the protocol (we stay in v4), as
we only add a field in the JSON-encoded handshake data:
Links:
~6.2.0(diff)~8.2.3v4.4.1Compare Source
Bug Fixes
RemoteSocket.datatype safe (#4234) (770ee59)SocketDatatype to custom namespaces (#4233) (f2b8de7)Links:
~6.1.0(diff)~8.2.3v4.4.0Compare Source
Bug Fixes
Features
socket.data(#4159) (fe8730c)Links:
~6.1.0(diff)~8.2.3v4.3.2Compare Source
Bug Fixes
Links:
~6.0.0~8.2.3v4.3.1Compare Source
Bug Fixes
Links:
~6.0.0~8.2.3v4.3.0Compare Source
For this release, most of the work was done on the client side, see here.
Bug Fixes
Features
Links:
~6.0.0(diff)~8.2.3(diff)v4.2.0Compare Source
Bug Fixes
Features
Links:
~5.2.0~7.4.2v4.1.3Compare Source
Bug Fixes
Links:
~5.1.0~7.4.2v4.1.2Compare Source
Bug Fixes
Links:
~5.1.0~7.4.2v4.1.1Compare Source
Bug Fixes
Links:
~5.1.0~7.4.2v4.1.0Compare Source
Blog post: https://socket.io/blog/socket-io-4-1-0/
Features
engine.io)engine.io)Links:
~5.1.0~7.4.2v4.0.2Compare Source
Bug Fixes
Links:
~5.0.0~7.4.2v4.0.1Compare Source
Bug Fixes
Links:
~5.0.0~7.4.2v4.0.0Compare Source
Blog post: https://socket.io/blog/socket-io-4-release/
Migration guide: https://socket.io/docs/v3/migrating-from-3-x-to-4-0/
Bug Fixes
Features
BREAKING CHANGES
io.to(...)now returns an immutable operatorPreviously, broadcasting to a given room (by calling
io.to()) would mutate the io instance, which could lead to surprising behaviors, like:Calling
io.to()(or any other broadcast modifier) will now return an immutable instance.Links:
~5.0.0~7.4.2v3.1.2Compare Source
Bug Fixes
Links:
~4.1.0~7.4.2v3.1.1Compare Source
Bug Fixes
Links:
~4.1.0~7.4.2