Instance-safe commands
Two instances of the same Module register independent command targets.
Connect Modules safely and load server data before a page renders.
Updated August 18, 2026 · 7 of 13
A public command exposes an internal Module function through a stable command ID and an explicit argument schema. Applications can target a particular Module instance without depending on the function's display name.
Two instances of the same Module register independent command targets.
Schema validation, timeout, cancellation, concurrency, and cleanup rules apply at runtime.
A Module can run a canonical server loader before render and hydrate its validated result as serverData.
Choose whether server-load failure stops rendering or supplies a configured fallback object.
onMount runs after hydration and is separate from lifecycle.serverLoad. Use server load for data required before render; use on-mount behavior for browser-only work.