• Decouple loader tree construction from children ordering: #97192
• [turbopack] Retain fewer stale cache versions and use a TTL: #96941
• Bump lightningcss: #97159

Huge thanks to @gnoff, @lukesandberg, and @mischnic for helping!

See CHANGELOG.md for details.

Full Changelog: https://github.com/rari-build/rari/compare/create-rari-app@0.5.21...create-rari-app@0.5.22

See CHANGELOG.md for details.

Full Changelog: https://github.com/rari-build/rari/compare/rari@0.15.9...rari@0.15.10

Release 2026-08-11 21:43

• solid-query: consume hydration data client-side via a provider-owned streaming channel (#11168) (67c817940) by @ryansolid

• @tanstack/solid-query@6.0.0-beta.8
• @tanstack/solid-query-devtools@6.0.0-beta.8
• @tanstack/solid-query-persist-client@6.0.0-beta.8

Release 2026-08-11 21:43

• solid-query: consume hydration data client-side via a provider-owned streaming channel (#11168) (67c817940) by @ryansolid

• @tanstack/solid-query@6.0.0-beta.8
• @tanstack/solid-query-devtools@6.0.0-beta.8
• @tanstack/solid-query-persist-client@6.0.0-beta.8

• #11168 67c8179 - chore: upgrade to solid v2 beta 33. @tanstack/solid-query now requires solid-js >= 2.0.0-beta.33 (peer range floor raised): the provider-owned hydration channel depends on beta.33's normalizeIterator buffered-replay conflation fix — on beta.32 and earlier, hydration that begins after multiple stream chunks have arrived silently drops later channel yields, leaving queries never primed and their components frozen.

• Updated dependencies [67c8179, 67c8179]:

  • @tanstack/solid-query@6.0.0-beta.8

• #11168 67c8179 - chore: upgrade to solid v2 beta 33. @tanstack/solid-query now requires solid-js >= 2.0.0-beta.33 (peer range floor raised): the provider-owned hydration channel depends on beta.33's normalizeIterator buffered-replay conflation fix — on beta.32 and earlier, hydration that begins after multiple stream chunks have arrived silently drops later channel yields, leaving queries never primed and their components frozen.

• Updated dependencies [67c8179, 67c8179]:

  • @tanstack/solid-query@6.0.0-beta.8

• #11168 67c8179 - chore: upgrade to solid v2 beta 33. @tanstack/solid-query now requires solid-js >= 2.0.0-beta.33 (peer range floor raised): the provider-owned hydration channel depends on beta.33's normalizeIterator buffered-replay conflation fix — on beta.32 and earlier, hydration that begins after multiple stream chunks have arrived silently drops later channel yields, leaving queries never primed and their components frozen.

• #11168 67c8179 - fix: prime the query cache during hydration through a provider-owned dehydration channel, so SSR-fetched queries come up warm instead of refetching on mount. QueryClientProvider streams dehydrated cache entries (query-core dehydrate() shapes) as each query settles during SSR — entries ride the same flush as the content that awaited them — and applies them on the client via query-core hydrate() (newer-wins) as they arrive, attaching each hydrated component's observer as soon as its entry is primed. The vestigial per-observer-result hydrationData copy is no longer serialized.

• #11168 67c8179 - chore: upgrade to solid v2 beta 33. @tanstack/solid-query now requires solid-js >= 2.0.0-beta.33 (peer range floor raised): the provider-owned hydration channel depends on beta.33's normalizeIterator buffered-replay conflation fix — on beta.32 and earlier, hydration that begins after multiple stream chunks have arrived silently drops later channel yields, leaving queries never primed and their components frozen.

• Updated dependencies [67c8179, 67c8179]:

  • @tanstack/solid-query@6.0.0-beta.8

• #11168 67c8179 - chore: upgrade to solid v2 beta 33. @tanstack/solid-query now requires solid-js >= 2.0.0-beta.33 (peer range floor raised): the provider-owned hydration channel depends on beta.33's normalizeIterator buffered-replay conflation fix — on beta.32 and earlier, hydration that begins after multiple stream chunks have arrived silently drops later channel yields, leaving queries never primed and their components frozen.

• #11168 67c8179 - fix: prime the query cache during hydration through a provider-owned dehydration channel, so SSR-fetched queries come up warm instead of refetching on mount. QueryClientProvider streams dehydrated cache entries (query-core dehydrate() shapes) as each query settles during SSR — entries ride the same flush as the content that awaited them — and applies them on the client via query-core hydrate() (newer-wins) as they arrive, attaching each hydrated component's observer as soon as its entry is primed. The vestigial per-observer-result hydrationData copy is no longer serialized.