Solid.js v2 compatibility for @tanstack/solid-query

[2wheeh]

Solid.js 2.0 beta has been released with several breaking changes that affect @tanstack/solid-query.

Import path changes:

• solid-js/store → solid-js (stores merged into main package)
• solid-js/web → @solidjs/web

API renames:

• mergeProps → merge
• splitProps → omit
• Suspense → Loading
• onMount → onSettled
• createEffect signature changed (compute → apply two-phase)

Behavioral changes:

• Batching by default (setters don't immediately update reads)

Questions

1. Is there a plan to support Solid v2 within v5, or will this wait for a future major (v6)?
2. Should we start a community PR for the adapter migration?

Ref: https://github.com/solidjs/solid/blob/next/documentation/solid-2.0/MIGRATION.md

[abhayclasher]

yo, solid v2 beta is a huge shift! usually maintainers wait for stable releases before committing to major version support, but a community PR would probs be the best way to get the ball rolling and show the demand. v5 is still the main focus, so an adapter update or a dedicated v2 compat branch is probs more likely than waiting all the way for v6. bet the crew would love the help if u wanna start a draft! ✌️

[2wheeh]

With Solid v2, I expect the adapter could become way thinner.

In v1, createResource was the only way to handle async (trigger Suspense, serialize async values for SSR, and handle hydration).
So the adapter had to wrap query-core's observer results through it, which required several workarounds (Promise wrapping, deep signal hack, custom Proxy, separate server/client subscribers).

In v2, async is a first-class capability of all computations — the signal graph handles serialization across the server→client boundary internally. A createMemo returning a Promise just works with <Loading>, SSR, and hydration without a separate primitive. This could remove the need for most of the adapter complexity.