@zerotal/flow 1.6.3 → 1.7.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zerotal/flow",
-  "version": "1.6.3",
+  "version": "1.7.2",
   "license": "MIT",
   "maturity": "stable",
   "private": false,
@@ -18,6 +18,7 @@
   },
   "files": [
     "CHANGELOG.md",
+    "api-surface.md",
     "src",
     "!src/**/*.test.ts",
     "!src/**/*.test.tsx",
@@ -46,14 +47,15 @@
     "@alpinejs/morph": "^3.14.9",
     "@alpinejs/persist": "^3.14.9",
     "@alpinejs/resize": "^3.14.9",
-    "@zerotal/core": "1.6.3",
-    "@zerotal/orm": "1.6.3",
-    "@zerotal/validator": "1.6.3",
+    "@zerotal/client": "1.7.2",
+    "@zerotal/core": "1.7.2",
+    "@zerotal/orm": "1.7.2",
+    "@zerotal/validator": "1.7.2",
     "alpinejs": "^3.14.9",
     "typescript": "^5.8.0"
   },
   "devDependencies": {
-    "@zerotal/broadcasting": "1.6.3",
+    "@zerotal/broadcasting": "1.7.2",
     "@types/alpinejs": "^3.13.10",
     "@types/alpinejs__anchor": "^3.13.1",
     "@types/alpinejs__collapse": "^3.13.4",

package/src/Component.ts

@@ -493,8 +493,19 @@ export abstract class Component {
 
   // ── @internal: framework bookkeeping, not part of the developer API ──────────
 
-  /** Set to true by hydrate() so the framework skips calling onMount(). @internal */
-  _skipMount = false;
+  // `_skipMount` used to live here, declared as "set to true by hydrate() so the
+  // framework skips calling onMount()". Nothing ever read it. Mount-skipping is
+  // structural and always has been: the router branches between `onHydrate()`
+  // and `onMount()`, and the action dispatcher calls `onMount()` only when an
+  // action asks for it.
+  //
+  // It was removed rather than wired up because wiring it would have been wrong.
+  // `$refresh` and `$mount` deliberately re-run `onMount()` on a page that was
+  // hydrated — so a flag whose stated meaning is "this page has been hydrated,
+  // do not mount it" would have broken both the moment anyone honoured it. An
+  // inert flag that reads as load-bearing is worse than none: the next person
+  // building render modes would reach for it, find it does nothing, and ship a
+  // double-mount. `hooks.test.ts` pins the real guarantee instead.
 
   /** Populated by flash() — read by the WS handler to emit flash frames. @internal */
   _flashes: FlashMessage[] = [];

package/src/browser/FlowBrowser.ts

@@ -76,8 +76,13 @@ export class FlowBrowser {
       // than on a sleep is what makes these tests deterministic: a slow boot
       // waits longer, and a bridge that never connects fails with a clear reason
       // instead of a mystery assertion further down.
+      //
+      // Guarded on `document.body` existing: the poll can land between a
+      // navigation committing and the body being parsed, and `null.getAttribute`
+      // throws out of `evaluate` rather than returning false — so the wait died
+      // with a TypeError instead of polling once more.
       await page.waitUntil(
-        `document.body.getAttribute("data-flow-connection") === "online"`,
+        `!!document.body && document.body.getAttribute("data-flow-connection") === "online"`,
         "Flow to connect its WebSocket",
         timeout,
       );
@@ -125,7 +130,7 @@ export class FlowBrowser {
 
     if (options.waitForConnection !== false) {
       await this.waitUntil(
-        `document.body.getAttribute("data-flow-connection") === "online"`,
+        `!!document.body && document.body.getAttribute("data-flow-connection") === "online"`,
         "Flow to connect its WebSocket",
         timeout,
       );