@net-mesh/browser 0.40.0 → 0.41.1

package/CHANGELOG.md

@@ -14,6 +14,60 @@ 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.41.1 — two pages can connect to each other at once
+
+- **`connectPeer` from both sides no longer cancels both attempts.** When
+  two pages called `connectPeer` on each other at the same moment, each
+  answer retired the answerer's own offer, both ran out their ICE
+  deadline, and the pair stayed relayed. Every game had to hand-code a
+  tie-break. The SDK now does it, on `BrowserNode` and `MeshSession`
+  alike:
+  - the page with the **lower** node id offers;
+  - the higher one answers an offer from that peer that arrived within
+    the offerer's ICE deadline instead of offering back, and answers one
+    that crosses its own offer while that is under way. Once an answer
+    has started, its outcome is the call's;
+  - `acceptPeer` while this surface's own `connectPeer` for the peer is
+    in flight takes that call's outcome.
+
+  Offers are learned from the surface's verified signal events. With
+  none, or with the peer's node id unknown, `connectPeer` behaves as
+  before. One offerer per pair is an attempt at a direct link, not a
+  guarantee of one: read `peerAttempt()`.
+- **`joinLobby`'s `close()` resolves only once its withdrawal has
+  settled.** An announcement replaces a node's whole tag set, so a
+  withdrawal still in flight when the page went on to `createLobby`
+  could land after the new listing and erase it. The withdrawal also
+  waits for any seeking announcement still in flight.
+- **`counters()` reports each drop reason.** The leaf's nested `drops`
+  object came back as the string `"[object Object]"`; nested groups now
+  flatten to dotted keys (`drops.<reason>`), each still an exact decimal
+  string.
+
+## 0.41.0 — the whole module surface is exported
+
+- **Every module-level export is reachable from an entry point.** Code
+  that builds its own transport or tooling on the primitives the
+  high-level verbs use no longer copies them out of the package:
+  - `@net-mesh/browser/netcode`: the wire helpers `eventPeer`,
+    `peerHex`, `encodeFrame`, `decodeFrame`, `chunkOf`,
+    `snapshotFrames` and the limits;
+  - `@net-mesh/browser/store`: the store internals (wire codec,
+    ledger, chunker, assembly, patch, owner and replica);
+  - the root: the peer driver, the org trampolines and refusal
+    constants, `StreamIdentityError` and the `LeafWasmOrg*` types;
+  - `leader`: `PromotionFailedEvent`.
+
+  Additive: nothing that was exported before changed.
+- **A host whose hex node id has no letters is joinable.** `joinStore`
+  read its `host` the way it reads an event's peer, where a string of
+  digits is decimal, so for about one host id in 1,800 the joiner
+  addressed a different node and could never join. An id the caller
+  holds (a lobby's host, a descriptor's `peerIdHex`, `nodeIdHex()`) is
+  now read as hex. The same fix covers the host store's own authority,
+  the region directory's hosts and the handoff link. 0.39 fixed the
+  joiner's own id; this is the host's.
+
 ## 0.39.0 — connectPeer waits for an attempt under way
 
 - **`connectPeer` no longer cancels an attempt that is still under

package/README.md

@@ -576,9 +576,11 @@ For views the rules can't express, write the projection yourself:
 audience })` (one per player). The declared rules still apply after it, so your
 code can hide more but never reveal a declared secret.
 
-**One tab per player.** All tabs of the same site in one browser profile share a
-single identity, so two tabs are the *same* player — and a player can't join
-itself. To test with two players on one machine, use two browser profiles, or
+**One tab per player.** With `rememberedIdentity()`, all tabs of the same site in
+one browser profile share a single identity once it is stored (two tabs that
+call it for the very first time at once can each create their own), so two tabs
+are the *same* player — and a player can't join itself. (Without it, every tab's `connect()` is a new
+player.) To test with two players on one machine, use two browser profiles, or
 two different browsers.
 
 **Announcements expire.** A host that announces once disappears from searches