Patch Changes
-
#11751
8a13b15- Move off Solid's internalsharedConfigonto its public hydration API. The hydrating-mount checks readisHydrating(), the server cache stream writes throughgetHydrationWriter()gated onisHydratable()(so<NoHydration>is still respected), anduseQueryconsumes its streamed entry withtakeHydrationValue().sharedConfigis internal in Solid 2.0 and absent from the publishedsolid-jsdeclarations, so the previous imports no longer type-check.These APIs ship in Solid
2.0.0-rc.13, so thesolid-js/@solidjs/webpeer floor is now>=2.0.0-rc.13. -
#11543
cb63f07- Follow Solid 2.0.0-rc.9. The packages build with@solidjs/babel-plugin(the Solid 2.0 compiler, matching the rc.9 runtime's delegated-event contract) and test under vite 8; thesolid-js/@solidjs/webpeer floor is2.0.0-rc.9.useQuery's setup-time snapshots (the meta projection's seed, the mount counts) now read the cache directly instead of through the hook's version signal. Under hydration, priming writes that signal during setup, and a write made during the hydration pass is held: a computation in the pass that reads it — tracked or not — is served the pre-write value and replays when the pass ends. For the hook's own derived nodes that replay is the takeover; for the computation instantiating the component (a<Loading>boundary's children) it was a remount, re-creating the hydrated component as a client render and letting cache writes reach the DOM while the stream was still open. -
Updated dependencies [
8a13b15,cb63f07]:- @tanstack/solid-query@6.0.0-rc.5