[Snyk] Upgrade socket.io-client from 4.4.1 to 4.5.2 #47

snyk-bot · 2022-09-28T04:57:13Z

Snyk has created this PR to upgrade socket.io-client from 4.4.1 to 4.5.2.

ℹ️ 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 3 versions ahead of your current version.
The recommended version was released 25 days ago, on 2022-09-02.

Release notes

Package name: socket.io-client

4.5.2 - 2022-09-02
Bug Fixes
- handle ill-formatted packet from server (c597023)
Links:
- Diff: 4.5.1...4.5.2
- Server release: 4.5.2
- engine.io-client version: ~6.2.1 (diff)
- ws version: ~8.2.3
Size of the bundles:

min min+gzip

socket.io.min.js 42.6 KB (-) 13.6 KB (-)

socket.io.msgpack.min.js 47.7 KB (-) 14.6 KB (-)

socket.io.esm.min.js 34.5 KB (-) 11.5 KB (-)
4.5.1 - 2022-05-17
There were some minor bug fixes on the server side, which mandate a client bump.

Links:
- Diff: 4.5.0...4.5.1
- Server release: 4.5.1
- engine.io-client version: ~6.2.1 (diff)
- ws version: ~8.2.3
Size of the bundles:

min min+gzip

socket.io.min.js 42.6 KB (-) 13.6 KB (-)

socket.io.msgpack.min.js 47.7 KB (-) 14.6 KB (-)

socket.io.esm.min.js 34.5 KB (-) 11.5 KB (-)

4.5.0 - 2022-04-23

Features

add details to the disconnect event (b862924)

The "disconnect" event will now include additional details to help debugging if anything has gone wrong.

Example when a payload is over the maxHttpBufferSize value in HTTP long-polling mode:

socket.on("disconnect", (reason, details) => {
console.log(reason); // "transport error"

// in that case, details is an error object
console.log(details.message); "xhr post error"
console.log(details.description); // 413 (the HTTP status of the response)

// details.context refers to the XMLHttpRequest object
console.log(details.context.status); // 413
console.log(details.context.responseText); // ""
});

add support for catch-all listeners for outgoing packets (74e3e60)

This is similar to onAny(), but for outgoing packets.

Syntax:

socket.onAnyOutgoing((event, ...args) => {
  console.log(event);
});

slice write buffer according to the maxPayload value (46fdc2f)

The server will now include a "maxPayload" field in the handshake details, allowing the clients to decide how many packets they have to send to stay under the maxHttpBufferSize value.

Links:

Diff: 4.4.1...4.5.0
Server release: 4.5.0
engine.io-client version: ~6.2.1 (diff)
ws version: ~8.2.3

Size of the bundles:

	min	min+gzip
socket.io.min.js	42.6 KB (+ 2.2 KB ⬆️)	13.6 KB (+ 0.5 KB ⬆️)
socket.io.msgpack.min.js	47.7 KB (+ 2.1 KB ⬆️)	14.6 KB (+ 0.4 KB ⬆️)
socket.io.esm.min.js	34.5 KB (+ 1.4 KB ⬆️)	11.5 KB (+ 0.2 KB ⬆️)

4.4.1 - 2022-01-06
This release only contains minor changes. Please see the diff for more details.

Links:
- Diff: 4.4.0...4.4.1
- Server release: 4.4.1
- engine.io-client version: ~6.1.1
- ws version: ~8.2.3
Size of the bundles:

min min+gzip

socket.io.min.js 40.4 KB (-) 13.1 KB (-)

socket.io.msgpack.min.js 45.6 KB (-) 14.2 KB (-)

socket.io.esm.min.js 33.1 KB (-) 11.3 KB (-)