Bot releases are visible (Hide)
engine.io-client@~6.5.2
(no change)ws@~8.11.0
(no change)Published by darrachequesne 9 months ago
There were some minor bug fixes on the server side, which mandate a client bump.
engine.io-client@~6.5.2
(no change)ws@~8.11.0
(no change)Published by darrachequesne 10 months ago
engine.io-client@~6.5.2
(no change)ws@~8.11.0
(no change)Published by darrachequesne about 1 year ago
Some bug fixes are included from the engine.io-client
package:
engine.io-client@~6.5.2
(diff)ws@~8.11.0
(no change)Published by darrachequesne over 1 year ago
Some bug fixes are included from the engine.io-client
package:
engine.io-client@~6.5.1
(diff)ws@~8.11.0
(no change)Published by darrachequesne over 1 year ago
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/webtransport
package:
import { WebTransport } from "@fails-components/webtransport";
global.WebTransport = WebTransport;
Added in 7195c0f.
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.
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.
~6.5.0
(diff)~8.11.0
(no change)Published by darrachequesne over 1 year ago
~6.4.0
(no change)~8.11.0
(no change)Published by darrachequesne over 1 year ago
~6.4.0
(no change)~8.11.0
(no change)Published by darrachequesne over 1 year ago
The trailing slash which was added by default can now be disabled:
import { io } from "socket.io-client";
const socket = io("https://example.com", {
addTrailingSlash: false
});
In the example above, the request URL will be https://example.com/socket.io
instead of https://example.com/socket.io/
.
Added in 21a6e12.
This commit adds some syntactic sugar around acknowledgements:
// without timeout
const response = await socket.emitWithAck("hello", "world");
// with a specific timeout
try {
const response = await socket.timeout(1000).emitWithAck("hello", "world");
} catch (err) {
// the server did not acknowledge the event in the given delay
}
Note: environments that do not support Promises will need to add a polyfill in order to use this feature.
Added in 47b979d.
This feature allows a client to reconnect after a temporary disconnection and restore its ID and receive any packets that was missed during the disconnection gap. It must be enabled on the server side.
A new boolean attribute named recovered
is added on the socket
object:
socket.on("connect", () => {
console.log(socket.recovered); // whether the recovery was successful
});
Added in 54d5ee0 (server) and b4e20c5 (client).
Two new options are available:
retries
: the maximum number of retries. Above the limit, the packet will be discarded.ackTimeout
: the default timeout in milliseconds used when waiting for an acknowledgement (not to be mixed up with the already existing timeout
option, which is used by the Manager during the connection)const socket = io({
retries: 3,
ackTimeout: 10000
});
// implicit ack
socket.emit("my-event");
// explicit ack
socket.emit("my-event", (err, val) => { /* ... */ });
// custom timeout (in that case the ackTimeout is optional)
socket.timeout(5000).emit("my-event", (err, val) => { /* ... */ });
In all examples above, "my-event" will be sent up to 4 times (1 + 3), until the server sends an acknowledgement.
Assigning a unique ID to each packet is the duty of the user, in order to allow deduplication on the server side.
Added in 655dce9.
~6.4.0
(diff)~8.11.0
(diff)Size of the bundles:
min | min+gzip | |
---|---|---|
socket.io.min.js | 45.8 KB (+ 3.2 KB ⬆️) | 14.5 KB (+ 0.9 KB ⬆️) |
socket.io.msgpack.min.js | 50.7 KB (+ 3.0 KB ⬆️) | 15.5 KB (+ 0.9 KB ⬆️) |
socket.io.esm.min.js | 37.0 KB (+ 2.5 KB ⬆️) | 12.3 KB (+ 0.8 KB ⬆️) |
Published by darrachequesne almost 2 years ago
This release contains a bump of the socket.io-parser
dependency, in order to fix CVE-2022-2421.
~6.2.3
~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 (-) |
Published by darrachequesne about 2 years ago
~6.2.1
~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 (-) |
Published by darrachequesne about 2 years ago
~6.2.1
(diff)~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 (-) |
Published by darrachequesne over 2 years ago
~3.5.0
~7.4.2
Published by darrachequesne over 2 years ago
There were some minor bug fixes on the server side, which mandate a client bump.
~6.2.1
(diff)~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 (-) |
Published by darrachequesne over 2 years ago
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); // ""
});
This is similar to onAny()
, but for outgoing packets.
Syntax:
socket.onAnyOutgoing((event, ...args) => {
console.log(event);
});
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.
~6.2.1
(diff)~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 ⬆️) |
Published by darrachequesne almost 3 years ago
This release only contains minor changes. Please see the diff for more details.
~6.1.1
~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 (-) |
Published by darrachequesne almost 3 years ago
socket.disconnect().connect()
usage (99c2cb8)socket.timeout(5000).emit("my-event", (err) => {
if (err) {
// the server did not acknowledge the event in the given delay
}
});
~6.1.1
(diff)~8.2.3
Size of the bundles:
min | min+gzip | |
---|---|---|
socket.io.min.js | 40.4 KB (+ 0.4 KB ⬆️) | 13.1 KB (+ 0.1 KB ⬆️) |
socket.io.msgpack.min.js | 45.6 KB (+ 0.4 KB ⬆️) | 14.2 KB (-) |
socket.io.esm.min.js | 33.1 KB (+ 0.3 KB ⬆️) | 11.3 KB (+ 0.2 KB ⬆️) |
Published by darrachequesne about 3 years ago
~6.0.1
~8.2.3
Size of the bundles:
min | min+gzip | |
---|---|---|
socket.io.min.js | 40.0 KB (-) | 13.0 KB (-) |
socket.io.msgpack.min.js | 45.2 KB (-) | 14.2 KB (-) |
socket.io.esm.min.js | 32.8 KB (-) | 11.1 KB (-) |
Published by darrachequesne about 3 years ago
~6.0.1
~8.2.3
Size of the bundles:
min | min+gzip | |
---|---|---|
socket.io.min.js | 40.0 KB (+ 0.1 KB ⬆️) | 13.0 KB (+ 0.1 KB ⬆️) |
socket.io.msgpack.min.js | 45.2 KB (+ 0.1 KB ⬆️) | 14.2 KB (+ 0.1 KB ⬆️) |
socket.io.esm.min.js | 32.8 KB (+ 0.1 KB ⬆️) | 11.1 KB (-) |
Published by darrachequesne about 3 years ago
An ESM bundle is now provided:
<script type="module">
import { io } from "https://cdn.socket.io/4.3.0/socket.io.esm.min.js";
const socket = io();
socket.emit("hello", "world");
</script>
The bundle size has also been greatly reduced, from 16.0 KB
to 12.9 KB
(min+gzip).
~6.0.1
(diff)~8.2.3
(diff)Size of the bundles:
min | min+gzip | |
---|---|---|
socket.io.min.js | 39.9 KB (-24.6 KB ⬇️) | 12.9 KB (-3.1 KB ⬇️) |
socket.io.msgpack.min.js | 45.1 KB (-25.6 KB ⬇️) | 14 KB (-2.6 KB ⬇️) |
socket.io.esm.min.js | 32.7 KB | 11.1 KB |