@componentor/fs 3.0.46 → 3.0.48

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@componentor/fs",
-  "version": "3.0.46",
+  "version": "3.0.48",
   "description": "High-performance OPFS-based Node.js fs polyfill with true sync API, VFS binary format, and bidirectional OPFS mirroring",
   "license": "MIT",
   "author": "Componentor",

package/readme.md

@@ -604,6 +604,18 @@ Make sure `opfsSync` is enabled (it's `true` by default). Files are mirrored to
 
 See [CHANGELOG.md](./CHANGELOG.md) for the full version history.
 
+### v3.0.48 (2026)
+
+**Fixes:**
+- Close the residual race left in the 3.0.47 broker-heartbeat fix: stop calling `close()` on the prior control port. The disentangle signal travels on a separate IPC pipe from the SW main channel with no ordering guarantee against `register-server`, so a `transfer-port` already queued in the SW inbox could still be dispatched against a detached `serverPort` and silently dropped. Letting the old port live until both endpoints become unreferenced (and GC-collected) keeps it routable through the swap and removes the window entirely
+
+### v3.0.47 (2026)
+
+**Fixes:**
+- Multi-tab broker survives service-worker idle-kill (≥30s on Chrome). Secondary tabs no longer fail with `[Shell] Failed to load cwd` after the SW is restarted — the leader re-registers on a 5 s heartbeat and the SW flushes any queued follower `transfer-port` messages to the new control port
+- Eliminate a race where heartbeat re-registration could silently drop in-flight follower `transfer-port` messages (new control port is now posted to the SW before the old one is closed)
+- `leader-changed` is broadcast exactly once at initial registration instead of on every heartbeat tick — prevents spurious EIO errors on long-running follower operations from leader-port reconnect churn
+
 ### v3.0.46 (2026)
 
 **Features:**