* refactor(solid): retire solid-router-ssr-query — Solid's native channels carry the Router + Query pairing
solid-query v6's QueryClientProvider serializes the request's cache into
Solid's hydration registry during SSR and primes the client cache from
it, so running the ssr-query transport alongside it ships every query
payload twice. The package's two runtime conveniences are each a few
lines of userland composition on public APIs: the provider wrap via the
router's Wrap option, and cache-driven redirect() errors handed to
router.navigate from the caches' config.onError.
Converts the three Solid Start e2e apps to the composition (all suites
green, including the redirect-from-query tests) and marks the package
deprecated for the v2 line.
Co-authored-by: Cursor <cursoragent@cursor.com>
* chore: changeset for the solid-router-ssr-query deprecation notice
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(solid-start): named single-flight source for router flight data
Solid's single-flight channel is becoming multi-source (solidjs/solid
653dd41e): mutation responses carry a keyed envelope of per-cache
slices, each routed to the consumer subscribed under its source id.
Today Start claims the single unnamed slot on both halves, which means
any other cache wanting mutation-response data (e.g. solid-query, whose
provider subscribes under "sq" in TanStack/query#11326) displaces the
router's — whichever registers last wins, silently.
The router's flight data now rides its own source id ("tsr"): the
server collector registers additively with registerFlightDataSource and
the client subscribes its consumer under the same id, so router
loader/match state and other caches' slices coexist on one round trip.
A user-supplied collectFlightData hook keeps the unnamed slot to itself,
adding data alongside the router's instead of displacing it.
Both halves feature-detect the protocol on the installed @solidjs/web
(it ships in the release after 2.0.0-rc.4) and fall back to the exact
previous unnamed-slot behavior on older versions; since client and
server resolve the same install, the halves cannot disagree.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(solid-router): loadFlightTarget, the cache-agnostic single-flight trigger
The router's half of flight collection as a public primitive: derive the
flight request for the mutation's target, run the matched routes' data
functions, hand the loaded router to the caller's collect() — any cache
(the router's own state, a query client) composes its extraction on top.
Start's collector now consumes it; errors are contained per Solid
Router's collector convention (flight data is an optimization, never a
mutation error).
Co-authored-by: Cursor <cursoragent@cursor.com>
* refactor(solid-start): require named flight sources, drop the pre-rc.5 fallback
@solidjs/web 2.0.0-rc.5 ships the multi-source single-flight protocol, so
the feature detection and cast shims bridging unreleased types come out:
the client subscribes directly under SOLID_START_FLIGHT_SOURCE, the server
registers its collector via registerFlightDataSource unconditionally (the
unnamed collectFlightData slot now always belongs to the user), and the
@solidjs/web peer floor moves to rc.5.
Co-authored-by: Cursor <cursoragent@cursor.com>
* test(e2e): expect the named single-flight source header
With the pre-rc.5 fallback stripped, the client advertises its named
source and the server echoes what it folded: X-Single-Flight is "tsr" on
both sides, not the legacy "true".
Co-authored-by: Cursor <cursoragent@cursor.com>
* chore(solid): bump solid-js, @solidjs/web, @solidjs/signals to 2.0.0-rc.6
Repo-wide (packages, examples, e2e apps, benchmarks) — a scoped bump
leaves the workspace mixed, and examples/benchmarks then build workspace
solid-start dists (which import registerFlightDataSource, rc.5+) against
their own @solidjs/web rc.4 resolution. rc.6 ships the named flight-data
source API this branch requires plus the settle-walk fix that unblocks
the Solid Query pairing. @tanstack/solid-start's peer floor moves to
rc.6.
The SSR bench helpers move onto rc.6's wire shape: scripted callers use
the data address (`<endpoint>/data/<id>`) — the bare address now answers
document traffic with the no-JS convention.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci: apply automated fixes
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
* chore(solid): bump to solid-js 2.0.0-rc.4 and @solidjs/vite-plugin 3.0.0-next.35
Also:
- Migrate the webpack example and docs off the deleted babel-preset-solid
onto @solidjs/babel-plugin (compiler packages were renamed in rc.3).
- Bump @rsbuild/plugin-solid to ^2.0.0-beta.2 so the rsbuild path compiles
with the rc-line preset.
- Adapt the server function transport to rc.4: function ids resolve from
the request url pathname (X-Server-Function header removed), and the
client reference derives its url from the configured endpoint.
- Wire per-call AbortSignals through Solid's new invoke() channel and
re-enable the previously skipped abort e2e tests.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* fix(solid-start): rc.4 CI fallout — rsbuild native loader ssr mode, benchmark wire protocol
- @rsbuild/plugin-solid >= 2.0.0-beta.1 compiles through its own solid
loader (native compiler) instead of registering babel-preset-solid, so
the babel preset patch never fired and node-target rsbuild bundles were
compiled in dom mode, throwing "Client-only API called on the server
side" at import. Patch the loader's solid options (generate ssr on
node targets, hydratable) alongside the legacy preset patch.
- The benchmark server-function request builders still spoke the pre-rc.4
wire protocol (id in the removed X-Server-Function-Id header, bare
endpoint url). Ids now ride the url pathname.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* chore(solid): bump @tanstack/solid-query to 6.0.0-rc.1
The rc.1 adapter is rewritten onto Solid 2.0's native async model
(TanStack/query#11308) and peer-requires solid-js >=2.0.0-rc.4, so it
rides this branch's rc.4 bump. Catalog entry plus the non-catalogued
solid-query-devtools pins move in lockstep.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>