From 34576a1ccda1ee192e8efbc653cb436111a9c5e8 Mon Sep 17 00:00:00 2001 From: Christophe Besson Date: Mon, 28 Sep 2026 12:29:20 +0200 Subject: fix(hub): say so when a lazily loaded view cannot be fetched A tab opened before a hub deploy got 404 for every module it had not loaded yet, and lazy.js kept its spinner for good. It now shows a notice with a Reload button and logs the failure. Co-Authored-By: Claude Opus 5.5 --- docs/MESHBAY_DESIGN.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'docs/MESHBAY_DESIGN.md') diff --git a/docs/MESHBAY_DESIGN.md b/docs/MESHBAY_DESIGN.md index e6bcece..78376a3 100644 --- a/docs/MESHBAY_DESIGN.md +++ b/docs/MESHBAY_DESIGN.md @@ -2518,7 +2518,12 @@ There is no folder-browsing protocol and this does not add one. 6. **Nothing to register for caching.** Every file under `static/` feeds the `/a//` fingerprint, subdirectories included, so a new or changed module moves the URL by itself — which matters for a module reached through the - registry, since nothing imports it by name. + registry, since nothing imports it by name. The other side of that: the hub + serves the current hash only, so **a tab opened before a deploy gets 404 for + every module it had not loaded yet**. `lazy.js` says so and offers a reload + rather than keeping its spinner — it used to swallow the rejection, and a + stale tab then spun for ever on every lazily loaded view with an empty + console. 7. **Add the file to the test file-set lists** — hook ordering, sticky headers, transport contracts. A file missing from those lists is never checked, which fails silently rather than loudly. -- cgit v1.2.3