Documentation

website.component.restore

First-page restoration context; no loading/motion bypass without ready data.

*context

*layout-listeners

*pending-layout

back-document?

(back-document?)

back-navigation?

(back-navigation?)

begin!

(begin! {:keys [hydrate? back?]})

direct-images!

(direct-images!)

direct-images?

(direct-images?)

Keep image policy reactive without invalidating its consumers when only the independent hydration-complete flag changes.

document-enter?

(document-enter?)

document-form

(document-form page)(document-form page lifecycle console)

Keep the native document’s React tree slots identical in Node, local capture and hydration. Empty lifecycle/console slots add no markup but preserve useId.

document-return?

(document-return?)

Native document history policy, installed before CSS and retained by BFCache.

hydrated!

(hydrated!)

hydrating-context

initial-hydration?

(initial-hydration?)

Capture the mount’s hydration decision without subscribing its render to the later hydration-complete update. Call from a hook initializer, not derived UI.

install-module-views!

(install-module-views! views)

layout-ready?

(layout-ready?)

listen-layout!

(listen-layout! callback)

local-document?

(local-document?)

navigate!

(navigate! path)

page-key

(page-key)

readiness-context

release-history!

(release-history!)

rendered-view?

(rendered-view? module view)

resumed!

(resumed! event)

skip-enter?

(skip-enter?)

Snapshot the mount’s entrance policy, like initial-hydration?. Completing hydration must not invalidate that mounted owner or its pending SSR children.

spa-back!

(spa-back!)

use-readiness!

(use-readiness! ready?)

Track mounted pending code/data inside the page, never speculative renders. Ready and terminal error views release their blocker after the DOM commit.