RobotWebTools / rclnodejs / 32113690306

91%

push

github

[Web runtime] Add reconnect-on-close to the Browser SDK (#1569)

Implements `RosClient`'s previously-reserved `reconnect` option (`web/client.js`, `_WsLink`).

- `{reconnect: true}` reopens the WS link with exponential backoff (500ms–30s, half-jitter) after a drop that follows a successful connect. The first connect attempt always rejects once rather than retrying forever, even when a connection error is followed by a close event.
- Active subscriptions are replayed on reopen, reusing the same `subId`, so existing `Subscription` handles keep working transparently.
- `RosClient.on`/`off` lifecycle events: `'disconnected'` (any unexpected drop), `'reconnecting'` (`{attempt, delay}`), `'reconnected'`.
- Any request affected by a drop — whether already in flight when it happened, or newly issued while a reconnect attempt is in progress — rejects with `code: 'connection_lost'`. The message adds `"; reconnecting"` only when a retry will actually happen, and stays plain `"connection lost"` when it won't.
- `ros.close()` always wins over reconnect and finalizes cleanly, whether called mid-backoff or while a reconnect attempt's socket is still opening.
- `web/index.d.ts`: `reconnect` documented as implemented; new `RosClientEventMap`/`ReconnectingDetail`; `on`/`off` declared on `RosClient`.
- `test/test-web-reconnect.js` (new, 8 tests): reconnect + subscription replay, in-flight/new-request rejection during a drop, default behavior with `reconnect` unset, first-connect-rejects-once, close() during backoff, close() never triggers a reconnect.

Fix: #1510

2196 of 2590 branches covered (84.79%)

Branch coverage included in aggregate %.

17593 of 19140 relevant lines covered (91.92%)

218.94 hits per line