Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
1
contributor
Commits on Oct 5, 2020
-
docs: remove reference to JSON3
The `json3` dependency, previously used for compatibility with IE6/7, was removed in [1] and included in `socket.io-parser@3.0.0` and `socket.io-client@2.0.0` ([2]). The slim build now only removes the debug dependency (~3KB min+gzip). [1] socketio/socket.io-parser@e39f5a8#diff-b9cfc7f2cdf78a7f4b91a753d10865a2 [2] ff4cb3e#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R28
-
refactor: remove gulp from the build
Plain npm scripts should be sufficient for our use case.
-
test: add Node.js 12 and 14 in the build matrix
Node.js 8 is removed, as it is now EOL.
-
-
-
Breaking change: - the encode() method is now synchronous Please note that the exchange [protocol][1] is left untouched and thus stays in version 4. Diff: socketio/socket.io-parser@3.4.1...4.0.0 [1] https://github.com/socketio/socket.io-protocol
Commits on Oct 6, 2020
-
chore: point towards the develop branch of the server
The package-lock.json file is temporarily removed in order to include the latest commits to the server and make the tests pass.
-
chore: include Engine.IO client v4
The ping-pong mechanism has been reverted (server now sends a ping and expects a pong from the client), so we cannot compute the latency like we did in previous versions. Release notes: https://github.com/socketio/engine.io-client/releases/tag/4.0.0
Commits on Oct 8, 2020
Commits on Oct 12, 2020
-
-
refactor: remove the packetBuffer array
The parser#encode() method is now synchronous, so the packetBuffer array is useless.
-
feat: split the events of the Manager and Socket
Previously, most of the events emitted by the Manager were also emitted by the Socket instances, but it was somehow misleading for the end users because they don't have the same meaning: - Manager: the state of the low-level connection (with connection and reconnection events) - Socket: the state of the connection to the Namespace (only 'connect', 'disconnect' and 'error') For example, the `reconnect` event: ```js socket.on("reconnect", () => { console.log(socket.connected); // might be false, which is a bit surprising }); ``` Breaking change: the Socket instance will no longer forward the events of its Manager Those events can still be accessed on the Manager instance though: ```js socket.io.on("reconnect", () => { // ... }); ``` -
feat: throw upon reserved event names
These events cannot be used by the end users, because they are part of the Socket.IO public API, so using them will now throw an error explicitly. Related: socketio/socket.io@f7ed81e
-
refactor: remove the 'connecting' event
This event was added in 4195680 But it does not convey the information that the Socket is actually sending a CONNECT packet to the server. It should maybe be moved to the Socket#onopen() method, but let's remove it for now as it is not documented anywhere.
-
refactor: remove the 'connect_timeout' event
The 'connect_timeout' event is now merged with the 'connect_error' event, and will now emit an Error object instead of a plain string.
Commits on Oct 13, 2020
-
- with `{ "type": "commonjs" }` in the package.json file ```js const io = require("socket.io-client"); const socket = io("/"); ``` - with `{ "type": "module" }` ```js import io from "socket.io-client"; const socket = io("/"); // or import { Manager } from "socket.io-client"; const manager = new Manager(); const socket = manager.socket("/"); ``` Related: https://nodejs.org/api/packages.html#packages_dual_commonjs_es_module_packages -
-
-
-
Commits on Oct 14, 2020
Commits on Oct 15, 2020
-
feat: move binary detection back to the parser
See socketio/socket.io-parser@285e7cd Breaking change: the Socket#binary() method is removed, as this use case is now covered by the ability to provide your own parser.
Commits on Oct 17, 2020
-
A volatile packet will be dropped if: - the socket is not connected - the low-level transport is not ready (for example, a HTTP POST request is already pending) Syntax: ```js socket.volatile.emit("volatile event", "might or might not be sent"); ``` -
Commits on Oct 25, 2020
-
feat: add bundle with msgpack parser
Pros: - events with binary content are sent as 1 WebSocket frame (instead of 2 with the default parser) - payloads with lots of numbers should be smaller Cons: - no IE9 support (https://caniuse.com/mdn-javascript_builtins_arraybuffer) - a slightly bigger bundle size (61.1 vs 59.9 KB) Source: https://github.com/darrachequesne/socket.io-msgpack-parser
Commits on Oct 26, 2020
-
feat: add support for catch-all listeners
Inspired from EventEmitter2 [1] The API is similar to the one on the server-side: ```js socket.onAny((event, ...args) => {}); socket.prependAny((event, ...args) => {}); socket.offAny(); // remove all listeners socket.offAny(listener); const listeners = socket.listenersAny(); ``` [1]: https://github.com/EventEmitter2/EventEmitter2 -
refactor: rename ERROR to CONNECT_ERROR
The meaning is not modified: this packet type is still used by the server when the connection to a namespace is refused. Breaking change: the Socket instance will now emit a "connect_error" event instead of "error" (which is not a reserved event anymore) ```js // before socket.on("error", () => {}); // after socket.on("connect_error", () => {}); ```
Commits on Oct 27, 2020
-
refactor: rework of the Manager events
- rename "connect_error" to "error" - remove "reconnecting" (duplicate of "reconnect_attempt") The updated list of events emitted by the Manager: - open: successful (re)connection - error: (re)connection failure (previously: "connect_error") or error after a successful connection - close: disconnection - ping: ping packet - packet: data packet - reconnect_attempt: reconnection attempt (previously: "reconnect_attempt" & "reconnecting") - reconnect: successful reconnection - reconnect_error: reconnection failure - reconnect_failed: reconnection failure after all attempts For reference, the Socket instance emits the following events: - connect: successful connection to a Namespace - connect_error: connection failure - disconnect: disconnection
There are no files selected for viewing
This file was deleted.