build(deps): update dependency socket.io-client to ^4.7.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
socket.io-client	^4.6.1 -> ^4.7.2

---

Release Notes

socketio/socket.io-client (socket.io-client)

v4.7.2

Compare Source

Some bug fixes are included from the engine.io-client package:

• webtransport: add proper framing (d55c39e)
• webtransport: honor the binaryType attribute (8270e00)

Dependencies

• engine.io-client@~6.5.2 (diff)
• ws@~8.11.0 (no change)

v4.7.1

Compare Source

Some bug fixes are included from the engine.io-client package:

• make closeOnBeforeunload default to false (a63066b)
• webtransport: properly handle abruptly closed connections (cf6aa1f)

Dependencies

• engine.io-client@~6.5.1 (diff)
• ws@~8.11.0 (no change)

v4.7.0

Compare Source

Bug Fixes

• properly report timeout error when connecting (5bc94b5)
• use same scope for setTimeout and clearTimeout calls (#​1568) (f2892ab)

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:

• https://w3c.github.io/webtransport/
• https://developer.mozilla.org/en-US/docs/Web/API/WebTransport
• https://developer.chrome.com/articles/webtransport/

For Node.js clients: until WebTransport support lands in Node.js, you can use the @fails-components/webtransport package:

import { WebTransport } from "@​fails-components/webtransport";

global.WebTransport = WebTransport;

Added in 7195c0f.

Cookie management for the Node.js client

When setting the withCredentials option to true, the Node.js client will now include the cookies in the HTTP requests, making it easier to use it with cookie-based sticky sessions.

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

const socket = io("https://example.com", {
  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 { defineConfig } from '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.

Dependencies

• engine.io-client@~6.5.0 (diff)
• ws@~8.11.0 (no change)

v4.6.2

Compare Source

Bug Fixes

• exports: move types condition to the top (#​1580) (7ead241)

Dependencies

• engine.io-client@~6.4.0 (no change)
• ws@~8.11.0 (no change)

---

Configuration

📅 Schedule: Branch creation - "on the 1st day of the month" in timezone Asia/Shanghai, 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

Preview Deployment

Build	URL	time
Sites	netlify preview	2023-08-05 03:16:40Z
Storybook	netlify preview	2023-08-05 03:17:33Z