Reactive compiled route records — [] until the table is loaded, a new array on setRoutes()/reload(). Table projections (useMenu) read this.
The history base ('' or e.g. '/admin/it') — absolute hrefs are base + path.
True while loaders run (navigations and query refetches).
True while a stale-while-revalidate refresh runs behind data already on
screen. Deliberately separate from isLoading: a stale hit commits real
data, so the page is showing something, not waiting for it. Only ever
true when a loader read opted into cache.staleTtl.
Latest navigation error (null after clear) — see useRouteError().
HOT PATH: patch a record's loader data directly (no loader run, no navigation) — for bus-command responses, websocket pushes, optimistic updates. One frozen snapshot, fully reactive.
Registrations auto-dispose with the component scope when made inside setup(); call the returned unsubscriber yourself elsewhere.
Re-fetch the table from the configured { url } source (admin tasks: deploys, permission changes). Coded error when no url is configured.
Absolute href (base included) for plain .
Reactive snapshot:
.value.location(URL state),.value.render(outlets),.value.data(loader results). One frozen object per commit.