@jsenv/navi 0.30.9 → 0.30.11

package/docs/actions.md

@@ -277,8 +277,9 @@ at best, a gesture late in a popup. It is for a parameter chosen inside the
 component and dying with it. Outside a component,
 `actionRunEffect(action, () => …)` is that same run declared once — it runs on
 the first truthy params, reruns when they change (unless the action declared
-`keep` and still holds the answer for the new ones), aborts when they go
-false — and the machinery `routeAction` is built on.
+`keep` and still holds the answer for the new ones, or only a prerun asked for
+them: that answer was read ahead for this arrival and is taken as it is), aborts
+when they go false — and the machinery `routeAction` is built on.
 
 **Which of the two it is, is decided by the parameter, not by what draws it.**
 If the parameter is in the address — a path param, a search param bound to a
@@ -311,6 +312,8 @@ It needs no `<Loading>`, and its failure reaches no boundary: nothing on screen
 asked for a prerun, so the owner's `{ run: true }` asks again, once, when it
 reads it. A failure of the owner's own run is shown, and asked again by a
 `rerun()`, never by a render. A head start still running is the owner's wait.
+A write that would ask a read again drops a head start instead: the owner
+finds it idle and asks for itself.
 
 `{ onLoad }` is what the screen does with the data **once, when it becomes
 known** — seed the fields someone is about to edit, focus something, remember

package/docs/drag_to_travel.md

@@ -250,7 +250,9 @@ A `RouteTravel` page not visited yet can only be built by the address moving, si
 a route's actions ask only while it matches. So the address moves once the hand has
 really pulled, 16px, and the page fills in under the finger. Before that its pane
 is empty and the box's background shows, unless `renderNeighbour` says what stands
-there. See
+there. What the page reads can be asked for before the hand arrives
+(`<RouteTravel prefetch>`, or `route.preload(params)`): it is still built under the
+finger, but from answers already there, so it shows no wait. See
 [navigation.md](./navigation.md#tabs-that-travel-routetravel).
 
 Both tell what follows them how far the row has come. `SlideContainer` writes

package/docs/dynamic_import.md

@@ -172,6 +172,7 @@ stays on the action, and a failed action is run again by whatever asks next —
 arrival, which shows its own failure, and every later hover alike.
 
 From code: `route.preload()` for a route about to be navigated to,
+`route.preload(params)` to also ask the reads its params decide,
 `preloadUrl(url)` for an address. A press that computes its destination has
 nothing to preload — the navigation itself asks.
 

package/docs/navigation.md

@@ -592,6 +592,26 @@ since the browser moves the row whatever the main thread is doing. So it renders
 with the page, and is worth keeping light. It is not the page: its route does not
 match yet, so it asks for nothing.
 
+**What a neighbour reads can be asked for ahead**, with `prefetch`. At rest, once
+the page on screen has its answers and has painted them, the box asks what the
+route actions of the next page will ask, then those of the previous one. The page
+is still built under the finger, but from answers already there: no wait shows.
+Off by default, since every page one stops on then costs the reads of two more.
+
+```jsx
+<RouteTravel routes={pages} renderNeighbour={renderNeighbour} prefetch>
+  <PlayerPage />
+</RouteTravel>
+```
+
+It is `route.preload(params)` for each of them: every route action of the route
+reads its params as if the address were `route.buildUrl(params)` (a weak state not
+given reads its default, any other one not given keeps what it holds), and the
+instance prerun is the one the arrival runs. A row driven by hand calls it the same
+way. Don't prerun the actions yourself: their params getters would then be written
+twice, and once one of them changes, the prefetch asks for an instance the arrival
+does not run.
+
 **The box has a height, or the document scrolls.** Pages may scroll themselves in a
 box the page gives a height to. If the document is what scrolls, it goes on doing
 so, and a page brought in stands where the reader is looking; what is lost is

package/package.json

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