This minimal browser reproduction shows a lost update when a Solid Query consumer mounts against warm, stale cache data.
pnpm install
pnpm startOpen the preview URL, wait until query.data contains Example item, and click Mount.
After clicking Mount, the page displays:
query.data
[{ "id": 1, "title": "Example item" }]
Mounted consumer output
[]
The query result contains the item, but the newly mounted consumer's derived signal remains empty.
This reproduces without Router or lazy routing, so TanStack Router is not involved. It is a Solid Query adapter regression: when a consumer mounts with warm, stale cache data, an immediate refetch causes the derived update to be lost.
| Solid | Solid Query | Result |
|---|---|---|
2.0.0-rc.6 |
6.0.0-rc.0 |
PASS |
2.0.0-rc.6 |
6.0.0-rc.2 |
FAIL |
This regression was introduced in Solid Query 6.0.0-rc.1 by the native async rewrite in PR #11308; rc.0 passes the same scenario.
#11351 covers a related createProjection notification bug, but its Solid-side fix is already included in Solid rc.6 and does not fix this cached-mount case. This is a distinct mount-time regression in the Solid Query adapter.