ta
TanStack
OSS
ta
Pipelines
Nx runs
Insights
Compare tasks
Analytics
Sign in
Toggle Sidebar
qu
query
Pipelines
fix(solid-query): stand the client suspend down while hydrating Suspending a tracked data read while Solid is claiming server-rendered DOM (sharedConfig.hydrating) bails the claim: the server rendered this content from settled data that the streaming hydration channel may not have primed on the client yet, so the throw leaves unclaimed server nodes and crashes the reactive system with 'Potential Infinite Loop Detected'. Reads during the hydration window return the store value instead — exactly the pre-suspense behavior — and the per-query hydration coordinator re-syncs them once their entry lands. Reproduced in a fullstack streaming-SSR testbed (queries still in flight at hydration time): crashes on every affected load without the guard, zero errors across repeated loads with it. 329/329 package tests pass. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
nx run-many --target=build --exclude=examples/** --exclude=integrations/**
⌘K
fix(solid-query): stand the client suspend down while hydrating
Succeeded
in
1s
Started
Linux
4 CPU cores
Copy command
nx run-many --target=build --exclude=examples/** --exclude=integrations/**
11292
606d09d
GitHub
Open on GitHub
Tasks
Resource Usage
ta
TanStack
OSS