@madojs/mado 0.13.0 → 0.13.1

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.13.1 - 2026-07-11
+
+### Fixed
+
+- Static capture now waits for asynchronous module bootstrap before reading
+  the runtime handshake. This removes a top-level-await race that surfaced on
+  slower Windows CI runners as `window.__MADO_STATIC__ was not installed`.
+
 ## 0.13.0 - 2026-07-11
 
 The final planned pre-v1 breaking release hardens ownership and freezes the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@madojs/mado",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "description": "A calm native-first web framework for sites and apps. Web Components, signals, routing, data, forms and browser-rendered static snapshots. Zero runtime dependencies.",
   "type": "module",
   "license": "MIT",

package/scripts/static/browser.mjs

@@ -212,6 +212,15 @@ async function captureRoute(browser, record, options) {
 
 async function waitForMadoStability(page, record, timeout) {
   try {
+    // DOMContentLoaded does not guarantee that an async module graph has
+    // finished evaluating. Apps may legitimately use top-level await during
+    // bootstrap (the modular starter restores auth this way), so wait for the
+    // runtime handshake instead of reading it once and racing slow runners.
+    await page.waitForFunction(
+      () => window.__MADO_STATIC__ !== undefined,
+      undefined,
+      { timeout },
+    );
     await withTimeout(
       page.evaluate(async () => {
         const runtime = window.__MADO_STATIC__;