[Snyk] Upgrade socket.io-client from 4.5.1 to 4.7.5 #59
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 was automatically created by Snyk using the credentials of a real user.
![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade socket.io-client from 4.5.1 to 4.7.5.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 14 versions ahead of your current version.
The recommended version was released on 2 months ago.
Release notes
Package name: socket.io-client
Bug Fixes
Links
engine.io-client@~6.5.2
(no change)ws@~8.11.0
(no change)There were some minor bug fixes on the server side, which mandate a client bump.
Links
engine.io-client@~6.5.2
(no change)ws@~8.11.0
(no change)Bug Fixes
Links
engine.io-client@~6.5.2
(no change)ws@~8.11.0
(no change)Some bug fixes are included from the
engine.io-client
package:Links
engine.io-client@~6.5.2
(diff)ws@~8.11.0
(no change)Some bug fixes are included from the
engine.io-client
package:Links
engine.io-client@~6.5.1
(diff)ws@~8.11.0
(no change)Bug Fixes
Features
Support for WebTransport
The Engine.IO client can now use WebTransport as the underlying transport.
WebTransport is a web API that uses the HTTP/3 protocol as a bidirectional transport. It's intended for two-way communications between a web client and an HTTP/3 server.
References:
For Node.js clients: until WebTransport support lands in Node.js, you can use the
@ fails-components/webtransport
package:global.WebTransport = WebTransport;
Added in 7195c0f.
Cookie management for the Node.js client
When setting the
withCredentials
option totrue
, the Node.js client will now include the cookies in the HTTP requests, making it easier to use it with cookie-based sticky sessions.withCredentials: true
});">
Added in 5fc88a6.
Conditional import of the ESM build with debug logs
By default, the ESM build does not include the
debug
package in the browser environments, because it increases the bundle size (see 16b6569).Which means that, unfortunately, debug logs are not available in the devtools console, even when setting the
localStorage.debug = ...
attribute.You can now import the build which includes the
debug
packages with a conditional import. Example with vite:import react from '@ vitejs/plugin-react'
export default defineConfig({
plugins: [react()],
server: {
port: 4000
},
resolve: {
conditions: ["development"]
}
})
Reference: https://v2.vitejs.dev/config/#resolve-conditions
Added in 781d753.
Links
~6.5.0
(diff)~8.11.0
(no change)Bug Fixes
types
condition to the top (#1580) (7ead241)Links
~6.4.0
(no change)~8.11.0
(no change)Bug Fixes
Links
~6.4.0
(no change)~8.11.0
(no change)Bug Fixes
Features
A new "addTrailingSlash" option
The trailing slash which was added by default can now be disabled:
addTrailingSlash: false
});">
In the example above, the request URL will be
https://example.com/socket.io
instead ofhttps://example.com/socket.io/
.Added in 21a6e12.
Promise-based acknowledgements
This commit adds some syntactic sugar around acknowledgements:
const response = await socket.emitWithAck("hello", "world");
// with a specific timeout
try {
const response = await socket.timeout(1000).emitWithAck("hello", "world");
} catch (err) {
// the server did not acknowledge the event in the given delay
}
Note: environments that do not support Promises will need to add a polyfill in order to use this feature.
Added in 47b979d.
Connection state recovery
This feature allows a client to reconnect after a temporary disconnection and restore its ID and receive any packets that was missed during the disconnection gap. It must be enabled on the server side.
A new boolean attribute named
recovered
is added on thesocket
object:Added in 54d5ee0 (server) and b4e20c5 (client).
Retry mechanism
Two new options are available:
retries
: the maximum number of retries. Above the limit, the packet will be discarded.ackTimeout
: the default timeout in milliseconds used when waiting for an acknowledgement (not to be mixed up with the already existingtimeout
option, which is used by the Manager during the connection)retries: 3,
ackTimeout: 10000
});
// implicit ack
socket.emit("my-event");
// explicit ack
socket.emit("my-event", (err, val) => { /* ... */ });
// custom timeout (in that case the ackTimeout is optional)
socket.timeout(5000).emit("my-event", (err, val) => { /* ... */ });
In all examples above, "my-event" will be sent up to 4 times (1 + 3), until the server sends an acknowledgement.
Assigning a unique ID to each packet is the duty of the user, in order to allow deduplication on the server side.
Added in 655dce9.
Links
~6.4.0
(diff)~8.11.0
(diff)Size of the bundles:
Related:
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:![](https://camo.githubusercontent.com/8fc841bed1d441815de38d59d99b0c6dc53672061448f430164debd16c7774bf/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f69497a4d6d453059574d784f43307a5a474d334c5451354d474d744f4745774d4330314d324d354e474d31596a4a6d5a5745694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496a4d7959545268597a45344c544e6b597a63744e446b7759793034595441774c54557a597a6b30597a56694d6d5a6c59534a3966513d3d)