Update dependency socket.io-client to v4.8.1 #21
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:
4.7.2
->4.8.1
Release Notes
socketio/socket.io (socket.io-client)
v4.8.1
Compare Source
Bug Fixes
Dependencies
engine.io-client@~6.6.1
(no change)ws@~8.17.1
(no change)v4.8.0
Compare Source
Features
Custom transport implementations
The
transports
option now accepts an array of transport implementations:Here is the list of provided implementations:
Fetch
fetch()
method.NodeXHR
XMLHttpRequest
object provided by thexmlhttprequest-ssl
package.XHR
XMLHttpRequest
object.NodeWebSocket
WebSocket
object provided by thews
package.WebSocket
WebSocket
object.WebTransport
WebTransport
object.Usage:
Fetch
NodeXHR
XHR
NodeWebSocket
WebSocket
WebTransport
(1) since v18.0.0
(2) since v21.0.0
Added in f4d898e and b11763b.
Test each low-level transports
When setting the
tryAllTransports
option totrue
, if the first transport (usually, HTTP long-polling) fails, then the other transports will be tested too:This feature is useful in two cases:
transports: ["websocket", "polling"]
)The only potential downside is that the connection attempt could take more time in case of failure, as there have been reports of WebSocket connection errors taking several seconds before being detected (that's one reason for using HTTP long-polling first). That's why the option defaults to
false
for now.Added in 579b243.
Bug Fixes
Dependencies
engine.io-client@~6.6.1
(diff and diff)ws@~8.17.1
(diff)v4.7.5
Compare Source
Bug Fixes
Links
engine.io@~6.5.2
(no change)ws@~8.11.0
(no change)v4.7.4
Compare Source
Bug Fixes
Links
engine.io@~6.5.2
(no change)ws@~8.11.0
(no change)v4.7.3
Compare Source
Bug Fixes
Links
engine.io@~6.5.2
(no change)ws@~8.11.0
(no change)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 this update again.
This PR was generated by Mend Renovate. View the repository job log.