[Snyk] Upgrade socket.io-client from 4.5.1 to 4.8.0

[SapiannykSerhii]

Snyk has created this PR to upgrade socket.io-client from 4.5.1 to 4.8.0.

ℹ️ 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 15 versions ahead of your current version.

• The recommended version was released on a month ago.

Release notes

Package name: socket.io-client

• 4.8.0 - 2024-09-21
  

  Features

  Custom transport implementations

  The transports option now accepts an array of transport implementations:

  import { io } from "socket.io-client";
  import { XHR, WebSocket } from "engine.io-client";

  const socket = io({
  transports: [XHR, WebSocket]
  });

  Here is the list of provided implementations:

  Transport	Description
  Fetch	HTTP long-polling based on the built-in fetch() method.
  NodeXHR	HTTP long-polling based on the XMLHttpRequest object provided by the xmlhttprequest-ssl package.
  XHR	HTTP long-polling based on the built-in XMLHttpRequest object.
  NodeWebSocket	WebSocket transport based on the WebSocket object provided by the ws package.
  WebSocket	WebSocket transport based on the built-in WebSocket object.
  WebTransport	WebTransport transport based on the built-in WebTransport object.

  Usage:

  Transport	browser	Node.js	Deno	Bun
  Fetch	✅	✅ (1)	✅	✅
  NodeXHR		✅	✅	✅
  XHR	✅
  NodeWebSocket		✅	✅	✅
  WebSocket	✅	✅ (2)	✅	✅
  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 to true, if the first transport (usually, HTTP long-polling) fails, then the other transports will be tested too:

  import { io } from "socket.io-client";

  const socket = io({
  tryAllTransports: true
  });

  This feature is useful in two cases:

  • when HTTP long-polling is disabled on the server, or if CORS fails
  • when WebSocket is tested first (with 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

  • accept string | undefined as init argument (bis) (60c757f)
  • allow to manually stop the reconnection loop (13c6d2e)
  • close the engine upon decoding exception (04c8dd9)
  • do not send a packet on an expired connection (#5134) (8adcfbf)

  Dependencies

  • engine.io-client@~6.6.1 (diff and diff)
  • ws@~8.17.1 (diff)
• 4.7.5 - 2024-03-14
• 4.7.4 - 2024-01-12
• 4.7.3 - 2024-01-03
• 4.7.2 - 2023-08-02
• 4.7.1 - 2023-06-28
• 4.7.0 - 2023-06-22
• 4.6.2 - 2023-05-31
• 4.6.1 - 2023-02-20
• 4.6.0 - 2023-02-06
• 4.6.0-alpha2 - 2023-02-04
• 4.6.0-alpha1 - 2023-02-03
• 4.5.4 - 2022-11-22
• 4.5.3 - 2022-10-15
• 4.5.2 - 2022-09-02
• 4.5.1 - 2022-05-17

from socket.io-client GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs