You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browse filesBrowse the repository at this point in the historyBrowse files
committed
refactor(solid-router): move hydration off sharedConfig onto public Solid 2.0 APIs
Replace solid-js internals with the public hydration surface shipped in
solid-js / @solidjs/web 2.0.0-rc.13 (solidjs/solid#3718):
- useHydrated: sharedConfig.hydrating -> isHydrating()
- serializeMatchTransfer: sharedConfig.context.serialize ->
getHydrationWriter().write, gated on isHydratable() (the old
context.noHydrate guard was dead in 2.0)
- primeRouterFromRegistry: raw _$HY.r reads, the tsr: prefix scan and
s/v unwrapping -> per-match takeHydrationValue()
- tests / external-SSR repro: drop the sharedConfig reset and _$HY
enumeration; the repro asserts entries server-side and consumption
through takeHydrationValue
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Bump solid-js and @solidjs/web to ^2.0.0-rc.13 (and @solidjs/vite-plugin to ^3.0.0-next.46), and raise the Solid peer floors to 2.0.0-rc.13.
11
+
12
+
@tanstack/solid-router moves off Solid's internal `sharedConfig` and the raw `_$HY` registry onto the public hydration API rc.13 ships (solidjs/solid#3718): `useHydrated` reads `isHydrating()`; the native SSR match transfer writes through `getHydrationWriter()` gated on `isHydratable()`, so it now respects `<NoHydration>`; and the client boot takes each match's entry with `takeHydrationValue()`.
0 commit comments