isHydratable
Whether the calling owner sits where hydration applies — not under
<NoHydration>, or back under a nested <Hydration> — so a value keyed
to this position reaches a hydrating client. On the server it also
requires the owner to belong to a render in progress. false with no
owner (a promise continuation, an IO callback): read it where the owner
is known. On the client, <Hydration> is a passthrough, so inside a
<NoHydration> zone (which renders only outside hydration) this stays
false even under a nested <Hydration>.
Solid decides this itself for its own values. A library writing keyed
values with getHydrationWriter() reads it to make the same decision.
Import
import { isHydratable } from "solid-js";Type signature
function isHydratable(): boolean;