Update socket.io 4.6.2 → 4.7.4 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ socket.io (4.6.2 → 4.7.4) · Repo · Changelog

Release Notes

4.7.4

Bug Fixes

• typings: calling io.emit with no arguments incorrectly errored (cb6d2e0), closes #4914

Links

• Diff: 4.7.3...4.7.4
• Client release: 4.7.4
• engine.io@~6.5.2 (no change)
• ws@~8.11.0 (no change)

4.7.3

Bug Fixes

• return the first response when broadcasting to a single socket (#4878) (df8e70f)
• typings: allow to bind to a non-secure Http2Server (#4853) (8c9ebc3)

Links

• Diff: 4.7.2...4.7.3
• Client release: 4.7.3
• engine.io@~6.5.2 (no change)
• ws@~8.11.0 (no change)

4.7.2

Bug Fixes

• clean up child namespace when client is rejected in middleware (#4773) (0731c0d)
• webtransport: properly handle WebTransport-only connections (3468a19)
• webtransport: add proper framing (a306db0)

Links

• Diff: 4.7.1...4.7.2
• Client release: 4.7.2
• engine.io@~6.5.2 (diff)
• ws@~8.11.0 (no change)

4.7.1

The client bundle contains a few fixes regarding the WebTransport support.

Links

• Diff: 4.7.0...4.7.1
• Client release: 4.7.1
• engine.io@~6.5.0 (no change)
• ws@~8.11.0 (no change)

4.7.0

Bug Fixes

• remove the Partial modifier from the socket.data type (#4740) (e5c62ca)

Features

Support for WebTransport

The Socket.IO server 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/

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

import { readFileSync } from "fs";
import { createServer } from "https";
import { Server } from "socket.io";
import { Http3Server } from "@fails-components/webtransport";
// WARNING: the total length of the validity period MUST NOT exceed two weeks (https://w3c.github.io/webtransport/#custom-certificate-requirements)

const cert = readFileSync("/path/to/my/cert.pem");

const key = readFileSync("/path/to/my/key.pem");
const httpsServer = createServer({

key,

cert

});
httpsServer.listen(3000);
const io = new Server(httpsServer, {

transports: ["polling", "websocket", "webtransport"] // WebTransport is not enabled by default

});
const h3Server = new Http3Server({

port: 3000,

host: "0.0.0.0",

secret: "changeit",

cert,

privKey: key,

});
(async () => {

const stream = await h3Server.sessionStream("/socket.io/");

const sessionReader = stream.getReader();
while (true) {

const { done, value } = await sessionReader.read();

if (done) {

break;

}

io.engine.onWebTransportSession(value);

}

})();
h3Server.startServer();

Added in 123b68c.

Client bundles with CORS headers

The bundles will now have the right Access-Control-Allow-xxx headers.

Added in 63f181c.

Links

• Diff: 4.6.2...4.7.0
• Client release: 4.7.0
• engine.io@~6.5.0 (diff)
• ws@~8.11.0 (no change)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 36 commits:

• chore(release): 4.7.4
• chore(tests): add a test for noArgs in a namespace
• chore(tests): fix issues due to client#id type change
• chore(tests): add type defs for expectjs and fix invalid expectations
• chore(tests): indicate a future ts error with version
• fix(typings): calling io.emit with no arguments incorrectly errored
• chore: bump socket.io-client version
• chore(release): 4.7.3
• fix: return the first response when broadcasting to a single socket (#4878)
• fix(typings): allow to bind to a non-secure Http2Server (#4853)
• docs(examples): add Vue client with CRUD example
• docs(examples): upgrade basic-crud-application to Angular v17
• refactor: cleanup after merge
• refactor(typings): improve emit types (#4817)
• test: build examples in the CI (#3856)
• docs: add Elephant.IO as PHP client library (#4779)
• docs(examples): add codesandbox configuration
• docs: add example with connection state recovery
• docs: improve example with express-session
• docs: use io.engine.use() with express-session
• docs: use "connection" instead of "connect"
• chore(release): 4.7.2
• fix(webtransport): properly handle WebTransport-only connections
• chore: bump engine.io to version 6.5.2
• fix: clean up child namespace when client is rejected in middleware (#4773)
• docs: update the list of supported Node.js versions
• docs(examples): add example with WebTransport
• chore(release): 4.7.1
• chore(release): 4.7.0
• ci: add Node.js 20 in the test matrix
• docs(examples): increase httpd ProxyTimeout value (2)
• docs(examples): increase httpd ProxyTimeout value
• feat: serve client bundles with CORS headers
• chore: bump engine.io to version 6.5.0
• fix: remove the Partial modifier from the socket.data type (#4740)
• docs(changelog): update the version range of the engine.io dependency

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #16.