[Snyk] Upgrade socket.io-client from 4.6.2 to 4.7.5 #161
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 has created this PR to upgrade socket.io-client from 4.6.2 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.
Release notes
Package name: socket.io-client
-
4.7.5 - 2024-03-14
- discard acknowledgements upon disconnection (34cbfbb)
- Diff: 4.7.4...4.7.5
- Server release: 4.7.5
-
4.7.4 - 2024-01-12
- Diff: 4.7.3...4.7.4
- Server release: 4.7.4
-
4.7.3 - 2024-01-03
- improve compatibility with node16 module resolution (#1595) (605de78)
- typings: accept string | undefined as init argument (5a3eafe)
- typings: fix the type of the socket#id attribute (f9c16f2)
- Diff: 4.7.2...4.7.3
- Server release: 4.7.3
-
4.7.2 - 2023-08-02
- webtransport: add proper framing (d55c39e)
- webtransport: honor the binaryType attribute (8270e00)
- Diff: 4.7.1...4.7.2
- Server release: 4.7.2
-
4.7.1 - 2023-06-28
- make closeOnBeforeunload default to false (a63066b)
- webtransport: properly handle abruptly closed connections (cf6aa1f)
- Diff: 4.7.0...4.7.1
- Server release: 4.7.1
-
4.7.0 - 2023-06-22
- properly report timeout error when connecting (5bc94b5)
- use same scope for setTimeout and clearTimeout calls (#1568) (f2892ab)
- https://w3c.github.io/webtransport/
- https://developer.mozilla.org/en-US/docs/Web/API/WebTransport
- https://developer.chrome.com/articles/webtransport/
import { WebTransport } from "@ fails-components/webtransport";
https://example.com", {
import { defineConfig } from 'vite'
- Diff: 4.6.2...4.7.0
- Server release: 4.7.0
- engine.io-client version:
- ws version:
-
4.6.2 - 2023-05-31
- exports: move
- Diff: 4.6.1...4.6.2
- Server release: 4.6.2
- engine.io-client version:
- ws version:
from socket.io-client GitHub release notesBug 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-clientpackage:Links
engine.io-client@~6.5.2(diff)ws@~8.11.0(no change)Some bug fixes are included from the
engine.io-clientpackage: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/webtransportpackage:global.WebTransport = WebTransport;
Added in 7195c0f.
Cookie management for the Node.js client
When setting the
withCredentialsoption 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
debugpackage 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
debugpackages 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
typescondition to the top (#1580) (7ead241)Links
~6.4.0(no change)~8.11.0(no change)Commit messages
Package name: socket.io-client
Compare
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:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs