Registers every declared store in the container, and hydrates it when the client is picking up
server-rendered markup.
Two things make this worth being first-party rather than a third-party store plus glue:
Hydration is not glue. The framework already ships a keyed, XSS-safe snapshot channel; a store
registered here reads its state out of it at registration time, which is before the first render.
Hydrating in an effect afterwards is what produces the flash of empty state every hand-rolled
integration suffers from.
Request isolation is the default. A store declared perRequest (the default) is bound as a
plain binding on the per-event container, so two visitors rendering at once cannot see each
other's state. A module-level singleton silently shares it, and nothing in development reveals it.
Registers every declared store in the container, and hydrates it when the client is picking up server-rendered markup.
Two things make this worth being first-party rather than a third-party store plus glue:
perRequest(the default) is bound as a plain binding on the per-event container, so two visitors rendering at once cannot see each other's state. A module-level singleton silently shares it, and nothing in development reveals it.