@jsenv/navi 0.29.161 → 0.29.162

package/docs/error_handling.md

@@ -256,6 +256,24 @@ finds a boundary that displays it, or reaches window on its own, since
 render loudly. Reporting it here too would be a second voice, and the wrong one:
 this module cannot see which of those happened.
 
+**And a render stopped in the middle read nothing after it.** `useAsyncData`
+delegates a failure by throwing it out of the render — that is how the error
+reaches the boundary. The render ends on that line, so a second `useAsyncData`
+below it, even one asking for `error: true`, is never called and never claims
+its own error. "Nobody read it" would then be true and meaningless: the order of
+two hook calls would decide whether the app is told it has a bug. So the throw
+speaks for the failures waiting for the same answer alongside it — a url change
+fails its route actions together — and none of them is reported. What is on
+screen is the failure the render was stopped at, which is the same story. A
+failure arriving _later_, after the page was replaced by what displays the first
+one, is not covered: nothing tells it apart from an action nobody reads.
+
+One error is never reported whoever looks at it: an **`OfflineError`**. The app
+declared the state that produced it and the request never left, so there is no
+bug to point at — it is data a screen shows. navi also cancels the window
+`error` event that displaying it produces in dev, which keeps the browser
+console and the jsenv overlay out of it ([offline.md](./offline.md)).
+
 So what reaches the report is an error **nothing looked at** — an action nobody
 reads, a prerun for a page never opened. And _when_ it is reported follows from
 that:

package/docs/offline.md

@@ -78,6 +78,13 @@ depends on what was asked:
   `reason` is the policy's value. `isOfflineError(error)` tells it apart from a
   request that left and never came back — that one is the app's `fetch`
   rejecting, and the app names it.
+
+  It is an error only in the way it travels. Nothing treats it as a bug: navi
+  never reports it as unhandled, and the window `error` event a boundary's
+  display produces in dev is cancelled, so neither the browser console nor the
+  jsenv overlay says anything. The person reads the screen; nobody else has to
+  hear about it.
+
 - **A write is refused before the press.** A control bound to a `POST`, `PUT`,
   `PATCH` or `DELETE` action — or any control inside a `<Form>` bound to one —
   is read-only while the policy holds, and answers the press with

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsenv/navi",
-  "version": "0.29.161",
+  "version": "0.29.162",
   "type": "module",
   "description": "Library of components including navigation to create frontend applications",
   "repository": {