krab_client
WASM island hydration runtime for the Krab full-stack Rust web framework.
krab_client runs in the browser. It locates the hydration markers emitted by
the server render, mounts the islands they describe, and wires up the reactive
signal graph so interactive regions become live without re-rendering the page.
Beyond hydration it exposes a client-side router: same-origin link clicks swap
the contents of the element marked data-krab-router-outlet and re-hydrate,
instead of reloading the document. Every failure path — no outlet, a bad
response, an offline network — falls back to a normal browser navigation.
Building
The result belongs on a page that loads it as a module and calls hydrate():
From Rust, hydrate_within(root) hydrates a subtree that arrived after first
paint, and unmount(root) releases what hydration created under it — call it
before removing hydrated markup, or its listeners, dynamic regions, and effects
stay alive for the life of the page.
Usage
[]
= "0.5"
Features
| Feature | Default | What it does |
|---|---|---|
web |
yes | The hydration runtime, the reconciler, and the router's browser half. Without it the crate is inert: hydrate() logs one line and returns. |
demo-islands |
yes | The bundled Counter / Toggle / Likes demo islands. Deprecated; removed in 0.6.0. |
debug |
no | Verbose console tracing of the hydration walk. |
web had no default through 0.1, 0.2, and 0.3, so the documented build command — which
did not name it — produced a ~15 KB stub instead of the ~198 KB runtime, and a
page loading it saw no error, just an island that never came alive. It is a
default as of 0.4.0. Nothing that already passed --features web needs to
change.
Take the crate without default features when you want the server half of
#[island] — the data-island / data-props wrapper markup that SSR emits and
the browser bundle later hydrates:
[]
= { = "0.5", = false }
Documentation
License
MIT