@net-mesh/browser 0.38.1 → 0.39.0

package/CHANGELOG.md

@@ -14,7 +14,47 @@ missing method at the call site rather than at install time. Unlike
 `@net-mesh/sdk`, this package never depends on `@net-mesh/core` — see
 the README on why it is a sibling package rather than a sub-path.
 
-## 0.38.1 — dual-stack anchors
+## 0.39.0 — connectPeer waits for an attempt under way
+
+- **`connectPeer` no longer cancels an attempt that is still under
+  way.** Every offer replaces the pair's link, so a second
+  `connectPeer` while the first was connecting cancelled it, and both
+  callers ended on the relay or in `iceTimeout`. That happened without
+  any page doing anything unusual: `joinLobby` reaches the host, then
+  the store it joins reaches it again before its first stream, and
+  netcode beside a store does the same. Now, per node (`BrowserNode`
+  and `MeshSession` alike):
+  - a call while another `connectPeer` for the same peer is in flight
+    resolves with that attempt's outcome, without offering again;
+  - a call while an `acceptPeer` for the peer is in flight waits for it,
+    and takes its outcome when that settles the pair: `direct`;
+    `iceTimeout` or `udpBlocked` (an offer straight after would almost
+    surely end the same way, a whole ICE deadline later, and the routed
+    session stays in place); or `superseded` naming a newer attempt
+    (an offer would cancel it). Only after an inconclusive answer
+    (`handshakeFailed`, `noAnnouncement`, a supersession with no
+    successor) does it offer;
+  - concurrent `acceptPeer` calls share one answer;
+  - the healthy-pair reading is taken inside that gate, just before any
+    offer. On a `MeshSession` it is a proxy round trip, and read ahead of
+    the gate it could go stale while an answer finished.
+
+  This completes the healthy-pair rule from 0.37.0 (a pair already
+  direct is never re-offered): a page or library may call `connectPeer`
+  "to be sure" at any point, without knocking out the link it is asking
+  about. Settled attempts are not remembered, so a later call after a
+  failure is a fresh attempt. Another tab's node is outside the rule, as
+  it is outside the surface.
+
+- **`createLocalMesh` reports a frame's peer as exact decimal**, as the
+  real node's `stream_data` does; it used to hand out the sender's hex
+  id. A hex id with no letters in it (about one random id in 1,800)
+  then read as a different node's decimal, and a store hosted on the
+  local mesh answered that joiner at an id that was not on the mesh. A
+  test that compared `peerNode` with `nodeIdHex()` compares it with the
+  decimal now.
+
+## 0.38.2 — dual-stack anchors
 
 An anchor can now serve IPv4 and IPv6 players at once
 (`net-mesh anchor serve --rtc-bind 0.0.0.0:7101 --rtc-bind '[::]:7101'`).