0
Fork 0
mirror of https://github.com/TanStack/router.git synced 2026-11-16 19:38:07 +00:00
Commit graph

6,566 commits

Author SHA1 Message Date
github-actions[bot]
f370e36b67
ci: Version Packages (beta) (#7866) release-2026-07-21-1438 @tanstack/solid-router-devtools@2.0.0-beta.21 @tanstack/solid-router-ssr-query@2.0.0-beta.27 @tanstack/solid-router@2.0.0-beta.26 @tanstack/solid-start-client@2.0.0-beta.26 @tanstack/solid-start-server@2.0.0-beta.26 @tanstack/solid-start@2.0.0-beta.27
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-07-21 16:33:32 +02:00
Brenley Dueck
714e11f191
Upgrade solidjs beta 21 (#7865) 2026-07-20 20:58:08 -05:00
github-actions[bot]
90652ce8dd
ci: Version Packages (beta) (#7851) release-2026-07-18-1930 @tanstack/solid-router-devtools@2.0.0-beta.20 @tanstack/solid-router-ssr-query@2.0.0-beta.26 @tanstack/solid-router@2.0.0-beta.25 @tanstack/solid-start-client@2.0.0-beta.25 @tanstack/solid-start-server@2.0.0-beta.25 @tanstack/solid-start@2.0.0-beta.26
* ci: changeset release (beta)

* ci: changeset release (beta) [Self-Healing CI Rerun]

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
2026-07-18 14:26:15 -05:00
Brenley Dueck
62f3b2697f
Upgrade solidjs beta 20 (#7850)
* chore: upgrade Solid v2 packages to 2.0.0-beta.20

Bumps solid-js and @solidjs/web from 2.0.0-beta.19 to 2.0.0-beta.20 and
vite-plugin-solid from 3.0.0-next.11 to 3.0.0-next.13 across packages,
examples, e2e apps, and benchmarks.

vite-plugin-solid 3.0.0-next.13 defaults to the new native JSX backend
(@dom-expressions/compiler), which is an incomplete milestone build that
cannot compile components with element children yet ("Only text and
expression component children are implemented in the AST-native
milestone"). Every vite-plugin-solid call site now passes
compiler: 'babel' to keep the babel-preset-solid pipeline until the
native compiler matures.

Also fixes two pins that had gone stale: the quickstart-webpack example's
direct babel-preset-solid pin (stuck on beta.18) and
@rsbuild/plugin-solid's babel-preset-solid lockfile resolution (also
beta.18), so the compiler and runtime are in lockstep everywhere.

Verified with solid-router test:unit (client + server modes) and
e2e/solid-start/basic (pnpm build + test:e2e:local).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: use the native JSX compiler (vite-plugin-solid default)

Removes the compiler: 'babel' escape hatch from all vite-plugin-solid
call sites, returning to next.13's default native backend
(@dom-expressions/compiler).

The native compiler's only unimplemented construct that this repo used
was a fragment passed as a component's child (dom mode only). The single
instance — the redundant <>{props.children}</> wrapper in solid-router's
ClientOnly — is removed; props.children is a valid JSX child on its own.

Verified: solid-router test:unit (client + server), e2e/solid-start/basic
(pnpm build + test:e2e:local), and a direct scan of all 1353 solid
.tsx/.jsx files in the repo through @dom-expressions/compiler in both
dom and ssr modes with zero failures.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-18 18:10:06 +02:00
github-actions[bot]
7a0cf36164
ci: Version Packages (beta) (#7835) release-2026-07-16-1505 @tanstack/solid-router-devtools@2.0.0-beta.19 @tanstack/solid-router-ssr-query@2.0.0-beta.25 @tanstack/solid-router@2.0.0-beta.24 @tanstack/solid-start-client@2.0.0-beta.24 @tanstack/solid-start-server@2.0.0-beta.24 @tanstack/solid-start@2.0.0-beta.25
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-07-16 17:01:11 +02:00
Brenley Dueck
ebe104c01c
Upgrade solidjs beta 19 (#7813)
* chore: upgrade Solid v2 packages to 2.0.0-beta.16

Bumps solid-js, @solidjs/web, and babel-preset-solid from 2.0.0-beta.15
to 2.0.0-beta.16 across packages, examples, e2e apps, benchmarks, and
the pnpm overrides in pnpm-workspace.yaml.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: upgrade Solid v2 packages to 2.0.0-beta.17

Bumps solid-js, @solidjs/web, and babel-preset-solid from 2.0.0-beta.16
to 2.0.0-beta.17 across packages, examples, e2e apps, and benchmarks.

The scoped babel-preset-solid overrides in pnpm-workspace.yaml are
removed instead of bumped: vite-plugin-solid@3.0.0-next.5 and
@rsbuild/plugin-solid@2.0.0-beta.0 both declare
'>=2.0.0-beta.0 <2.0.0-experimental.0', which resolves to the newest
v2 beta on its own, while Solid 1.x consumers keep babel-preset-solid
1.x. A stale override here silently kept the beta.16 compiler (with
its broken omitLastClosingTag marker handling) in the build pipeline.

The @dom-expressions/* scope is added to minimumReleaseAgeExclude,
covering the renamed compiler package (@dom-expressions/babel-plugin-jsx,
formerly babel-plugin-jsx-dom-expressions).

Two unrelated loose specs are pinned to their locked versions because
re-resolving the lockfile pulled broken releases: @platformatic/flame
1.7.0 fails pnpm's trust-downgrade policy, and the nitro-nightly
'latest' tag depends on an unpublished h3 version.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(solid-router): suspend on the match loadPromise only during SSR

On the client, returning the loadPromise from MatchInner's pending
branch keeps a live async source in the tree whenever a match is
pending. Since Solid 2.0.0-beta.16, that routes every signal write
into a transition hold for the rest of the flush, which breaks
router-core's synchronous write-then-load flows: invalidate() on a
notFound match never re-ran the loader, and writes to unrelated
signals were held too.

SSR keeps the suspension so the streaming engine waits for the match
to settle; the client now renders just the pending component.

Verified on beta.17: without this, "re-runs loaders that throw
notFound() when invalidated via HMR filter" and "keeps rendering a
route notFoundComponent when loader returns notFound() after
invalidate" fail.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(lockfile): restore all @rspack/binding@2.0.8 platform binaries

The lockfile entry for @rspack/binding@2.0.8 only listed the
darwin-arm64 binding, so linux CI runners had no matching native
binding and rspack fell back to a hoisted 2.0.0 binary, crashing the
bundle-size benchmark with a core/binding version mismatch.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: add changesets for solid-js beta.17 upgrade and SSR-only match suspension

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(examples): replace broken nitro-nightly pin with nitro beta in start-rscs

The pinned nitro-nightly@4.0.0-20251010 self-imports 'nitro/runtime/meta',
which under pnpm's isolated layout resolves to the hoisted nitro 3.x beta
and crashes vite config loading. Mirrors upstream fix e65f0c84c1 (#7809).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: upgrade vite-plugin-solid to next.7

* fix(solid-router): retain manifest stylesheets across navigation

* chore: upgrade Solid v2 packages to 2.0.0-beta.18 and vite-plugin-solid to next.8

Bumps solid-js, @solidjs/web, and babel-preset-solid from 2.0.0-beta.17
to 2.0.0-beta.18 and vite-plugin-solid from 3.0.0-next.7 to 3.0.0-next.8
(which pins @dom-expressions/jsx-compiler to 0.50.0-next.21) across
packages, examples, e2e apps, and benchmarks.

vite-plugin-solid is added to minimumReleaseAgeExclude: Solid publishes
plugin prereleases in lockstep with the runtime betas, often minutes
before we bump, and pnpm's 24h release-age gate otherwise filters the
new version with a misleading NO_MATCHING_VERSION error.

Verified: solid-router unit tests (client + server modes), solid-start
basic e2e (80 passed), solid-router basic-file-based e2e (120 passed),
and all 17 bundle-size benchmark scenarios build cleanly.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(start-plugin-core): select client entry chunk by facade module instead of asserting a single entry

vite-plugin-solid >= 3.0.0-next.6 emits a facade chunk for every
dynamically imported project module during SSR client builds (to keep
its own manifest lookups stable), and emitted chunks are flagged
`isEntry` just like the configured entry. The start manifest capture
plugin asserted the client bundle contains exactly one entry chunk, so
every solid-start app failed to build with "multiple entries detected".

The capture plugin now receives the resolved client entry path and picks
the entry chunk whose facadeModuleId matches it; other entry-flagged
chunks are treated as ordinary chunks. When no chunk matches, a single
entry is still accepted as before, and the multiple-entries error now
lists every entry chunk with its facade module to ease diagnosis.

Verified with fresh package builds: previously failing memory-server
solid benchmark targets, all 17 bundle-size scenarios, solid-start basic
build + e2e (80 passed), react-start basic build, and the
start-plugin-core unit suite (494 tests).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* ci: apply automated fixes

* test(start-plugin-core): pass getClientEntry to startManifestPlugin in dev manifest test

Fixes the type tests after startManifestPlugin gained a required
getClientEntry option.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Revert "fix(start-plugin-core): select client entry chunk by facade module instead of asserting a single entry"

This reverts commit d0f4926ec0.

* chore: upgrade vite-plugin-solid to 3.0.0-next.10

next.10 ships the fix for the lazy facade entry reclassification under
rolldown-vite (solidjs/vite-plugin-solid#269): assigning isEntry = false
instead of deleting the property, so the reclassification actually
propagates through rolldown's bundle proxies and downstream plugins no
longer see every lazy facade chunk as an application entry. This is the
proper replacement for the reverted start-plugin-core workaround
(see a1ee1638f5) — the strict single-entry assertion now holds again.

Verified: e2e/solid-start/basic build + e2e suite (80 passed),
solid-router test:unit client (814) + server (2) modes,
start-plugin-core unit tests (486).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: upgrade solid-js/@solidjs/web to 2.0.0-beta.19 and vite-plugin-solid to 3.0.0-next.11

vite-plugin-solid 3.0.0-next.11 peer-requires solid-js and @solidjs/web
>=2.0.0-beta.19, so the Solid v2 packages are bumped in lockstep across
all workspace pins (packages, examples, e2e, benchmarks).

Verified: e2e/solid-start/basic build succeeds — no "multiple entries
detected" error from start-manifest-capture-client-build; solid-router
test:unit client (814 passed) + server (2 passed) modes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* chore: upgrade solid-js/@solidjs/web to 2.0.0-beta.19 and vite-plugin-solid to 3.0.0-next.11 [Self-Healing CI Rerun]

* chore: upgrade solid-js/@solidjs/web to 2.0.0-beta.19 and vite-plugin-solid to 3.0.0-next.11 [Self-Healing CI Rerun]

* fix(e2e): make prerender builds hermetic to deflake build:vite:prerender

The prerender crawl runs inside `vite build` and SSRs /posts and every
crawled /posts/$postId. The `import.meta.env.VITE_NODE_ENV === 'test'`
switch to the local dummy server was inlined away at build time because
Playwright only sets that env for the test-time webServer, never for the
nx build target — so build-time SSR fetched the real
jsonplaceholder.typicode.com from CI. When that public API stalled, the
page never sent headers and the build died after undici's 5-minute
headers timeout (UND_ERR_HEADERS_TIMEOUT).

Fix, applied to the react/solid/vue basic apps alike:
- Resolve the posts/users API base URL at request time from process.env
  (same pattern users.tsx already used) instead of build-time inlining,
  so the built app honors whatever dummy server the harness is running.
- Add e2eStartDummyServerForBuild() to @tanstack/router-e2e-utils and
  call it from the apps' vite configs in prerender mode: it starts the
  dummy server on a free port for the lifetime of the build, exposes it
  via VITE_NODE_ENV/VITE_EXTERNAL_PORT, and unrefs everything so the
  build process can exit.

Verified: nx run tanstack-solid-start-e2e-basic:build:vite:prerender
passes (47 pages prerendered, dummy server used, tsc clean), prerendered
posts/index.html contains the expected content, and the server bundle
now keeps the runtime env check instead of a hardcoded external URL.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* ci: apply automated fixes

* chore: upgrade solid-js/@solidjs/web to 2.0.0-beta.19 and vite-plugin-solid to 3.0.0-next.11 [Self-Healing CI Rerun]

* fix(e2e): harden prerender-build dummy server and log fetch targets

CI still hit UND_ERR_HEADERS_TIMEOUT during build:vite:prerender after
de2132af1b. The failure pattern (fetch logs print instantly, then a
5-minute stall) means the posts fetches still reached the real external
API in that run: the dummy server resolves in milliseconds in-process,
and a non-listening port would fail instantly with ECONNREFUSED.

One way that can happen: e2eStartDummyServerForBuild() early-returned
whenever VITE_EXTERNAL_PORT was already present in the environment,
skipping both the server start AND setting VITE_NODE_ENV — leaving the
runtime URL check pointing at jsonplaceholder. Guard on a globalThis
flag instead and always set both env vars.

Also, to make the next failure diagnosable and survivable:
- fetchPost/fetchPosts (react/solid/vue basic) now log the base URL they
  fetch from, so CI output shows whether the dummy server was used.
- prerender configs set retryCount: 2 / retryDelay: 1000 so a transient
  hang retries instead of failing the whole build.

Verified: nx run tanstack-solid-start-e2e-basic:build:vite:prerender
passes with "Fetching posts from http://localhost:<port>..." in the log
and 47 pages prerendered.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
2026-07-16 16:17:49 +02:00
Brenley Dueck
2bb318bdcf fix(benchmarks): Solid v2 type fixes for new benchmark scenarios
- jsxImportSource solid-js -> @solidjs/web in the new scenario
  tsconfigs (Solid 2's JSX types moved; with the old value tsc fell
  back to React's JSX namespace and rejected solid components)
- createRenderEffect one-arg calls -> v2 (compute, effect) signature
  in the loaders, search-params, and nested-params solid scenarios,
  matching the existing client-nav solid app

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-04 07:34:04 -05:00
Brenley Dueck
26d94d93fc fix(benchmarks): adapt new solid benchmarks from main to Solid v2
main's new client-nav scenarios and memory benchmarks were written for
Solid 1.x and fail against this branch's Solid 2 toolchain:

- import render/HydrationScript from @solidjs/web instead of solid-js/web
- memory benchmark manifests: solid-js 2.0.0-beta.15, @solidjs/web,
  vite-plugin-solid ^3.0.0-next.5 (matching client-nav)
- Suspense -> Loading, and createResource -> router Await in the
  memory-server solid scenarios
- skip the streaming-peak solid bench: Solid 2's renderToStream emits
  </body></html> with the shell and streams deferred Loading content
  after it, so router-core's transformStreamWithRouter tail-buffers the
  ~200 kB of deferred sections and throws 'SSR stream tail exceeded
  maximum buffer' (MAX_TAIL_CHARS = 64 kB). Needs a transformer-level
  fix on this branch before the scenario can run.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-04 07:08:08 -05:00
Brenley Dueck
01dbb52d06 fix(lockfile): restore @rspack/binding@2.0.8 platform binaries
pnpm install --lockfile-only on darwin-arm64 dropped all other platform
optionalDependencies for @rspack/binding@2.0.8, causing the bundle-size
benchmark on Linux CI to fall back to a stale 2.0.0 binding
("Unmatched version @rspack/core@2.0.8 and @rspack/binding@2.0.0").
Restored the full platform list to match main's lockfile.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-04 06:46:49 -05:00
Brenley Dueck
adc6ed5712 Merge remote-tracking branch 'upstream/main' into solid-router-v2-pre
# Conflicts:
#	benchmarks/client-nav/package.json
#	examples/solid/authenticated-routes-firebase/package.json
#	examples/solid/authenticated-routes/package.json
#	examples/solid/basic-default-search-params/package.json
#	examples/solid/basic-devtools-panel/package.json
#	examples/solid/basic-file-based/package.json
#	examples/solid/basic-non-nested-devtools/package.json
#	examples/solid/basic-solid-query-file-based/package.json
#	examples/solid/basic-solid-query/package.json
#	examples/solid/basic-ssr-file-based/package.json
#	examples/solid/basic-ssr-streaming-file-based/package.json
#	examples/solid/basic-virtual-file-based/package.json
#	examples/solid/basic-virtual-inside-file-based/package.json
#	examples/solid/basic/package.json
#	examples/solid/deferred-data/package.json
#	examples/solid/i18n-paraglide/package.json
#	examples/solid/kitchen-sink-file-based/package.json
#	examples/solid/kitchen-sink-solid-query-file-based/package.json
#	examples/solid/kitchen-sink-solid-query/package.json
#	examples/solid/kitchen-sink/package.json
#	examples/solid/large-file-based/package.json
#	examples/solid/location-masking/package.json
#	examples/solid/navigation-blocking/package.json
#	examples/solid/quickstart-esbuild-file-based/package.json
#	examples/solid/quickstart-file-based/package.json
#	examples/solid/quickstart-rspack-file-based/package.json
#	examples/solid/quickstart-webpack-file-based/package.json
#	examples/solid/quickstart/package.json
#	examples/solid/router-monorepo-simple-lazy/package.json
#	examples/solid/router-monorepo-simple-lazy/packages/router/package.json
#	examples/solid/router-monorepo-simple/package.json
#	examples/solid/router-monorepo-simple/packages/router/package.json
#	examples/solid/router-monorepo-solid-query/package.json
#	examples/solid/router-monorepo-solid-query/packages/router/package.json
#	examples/solid/scroll-restoration/package.json
#	examples/solid/search-validator-adapters/package.json
#	examples/solid/start-basic-auth/package.json
#	examples/solid/start-basic-authjs/package.json
#	examples/solid/start-basic-cloudflare/package.json
#	examples/solid/start-basic-netlify/package.json
#	examples/solid/start-basic-nitro/package.json
#	examples/solid/start-basic-solid-query/package.json
#	examples/solid/start-basic-static/package.json
#	examples/solid/start-basic/package.json
#	examples/solid/start-bun/package.json
#	examples/solid/start-convex-better-auth/package.json
#	examples/solid/start-counter/package.json
#	examples/solid/start-i18n-paraglide/package.json
#	examples/solid/start-large/package.json
#	examples/solid/start-streaming-data-from-server-functions/package.json
#	examples/solid/start-supabase-basic/package.json
#	examples/solid/start-tailwind-v4/package.json
#	examples/solid/view-transitions/package.json
#	examples/solid/with-framer-motion/package.json
#	examples/solid/with-trpc/package.json
#	package.json
#	packages/solid-router/CHANGELOG.md
#	packages/solid-router/package.json
#	packages/solid-start-client/CHANGELOG.md
#	packages/solid-start-client/package.json
#	packages/solid-start-server/CHANGELOG.md
#	packages/solid-start-server/package.json
#	packages/solid-start/CHANGELOG.md
#	packages/solid-start/package.json
#	pnpm-lock.yaml
#	pnpm-workspace.yaml
2026-07-04 06:24:24 -05:00
Flo
a3e24c35a5
bench(memory): prefix client and server benchmark names (#7743) 2026-07-03 22:29:29 +02:00
Flo
d644dbb5c2
bench(memory): settle-until-quiescent GC barrier between iterations (#7739)
* bench(memory): settle-until-quiescent GC barrier between iterations

The fixed-turn settle before the pinned collection was hardware-fragile:
teardown needing one more event-loop turn on a given runner leaked a whole
payload of garbage past the collection point and flipped the measured peak
bimodally (serialization-payload solid/react resurfacing the pre-#7730
6.2MB attractor on some CI runners). Replace it with an adaptive barrier
that hops and collects until the post-GC heap size stops moving, with a
minimum-turn floor matching the fixed count it replaces (React's stream
teardown spans several turns and races a shorter floor).

Also pin collections in request-churn and the aborted-requests drain:
their peak floated on GC scheduling even with bit-identical work (18%
spread on CI for solid churn). Reachable accumulation stays visible to
the metric - a forced collection cannot reclaim leaked or cached objects,
it only removes floating garbage, whose collection timing was the
dominant cross-run noise source. Verified with a synthetic reachable
leak: +4.7% peak over a 0.6% A/A noise floor, where the old 18% noise
would have swallowed it.

Local A/A spreads (3x codspeed run per suite): solid <=1%, react <=2.2%
except request-churn (rare +130KB mode, framework teardown variance),
vue <=2.3% except aborted-requests (~8%, intra-iteration work variance,
down from 21% on CI).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* bench(memory): fixed-count settle barrier, drop adaptive quiescence exit

The adaptive exit (collect until post-GC heap size stops moving) made the
collection points land at data-dependent turns on CI: heap readings never
fully stabilize there, so the exit point - and every subsequent GC point -
shifted between identical runs. The first CI A/A pair showed it flipping
serialization-payload (vue) to a 6MB mode (67%), inflating peak-large-page
(vue) 3.4x, and adding 7-8% swings to the react/vue abort scenarios, while
fixing the solid suite.

Every step is now a fixed count: 16 settle turns (enough for React/Vue
multi-turn teardown that the original 2-turn barrier raced), one pinned
collection, one turn, one more collection for finalizer fallout. Fixed
counts make the GC points identical across runs by construction, which is
the property the barrier exists to provide.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* bench(memory): size iteration counts to the 2-10s measured-run window

On CI (eBPF instrument + --no-opt) one pinned iteration costs ~0.1-0.6s,
so the previous counts put request-churn at ~36s measured and the error
-paths/server-fn benches at 0.1-0.5s - outside the useful 2-10s range in
both directions. Retune: request-churn/aborted-requests/error-paths/
server-fn-churn to 40 iterations, serialization-payload to 12;
peak-large-page and streaming-peak already sit in range at 20.

The floor is raised by pinning error-paths and server-fn-churn rather
than inflating their iteration counts: thousands of unpinned iterations
would cross V8's own GC scheduling and reintroduce the timing noise the
barrier removes, while the pin's fixed per-iteration cost lifts them into
range at 40 iterations and makes their collection points deterministic.

Note: fewer churn iterations proportionally shrink the accumulation
window, so peak-based leak sensitivity drops accordingly; leaks remain
visible in total-allocated (forced compactions re-copy the growing live
set every iteration).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* bench(memory): disable V8 bytecode flushing in memory bench workers

The retuned (shorter) runs exposed a recurring V8 internal event - a
+7-13MB allocation burst with the signature of bytecode flush + lazy
recompile - that lands inside or outside the measured window at random,
flipping peaks by whole MBs between identical CI runs (request-churn vue
785KB vs 3.2MB). The pinned collections age code fast enough for V8 to
flush unused bytecode mid-run; --no-flush-bytecode keeps compiled code
alive for the process lifetime so the measured window sees no recompile
bursts. Vite's mergeConfig concatenates the scenario's test.execArgv with
the flags the CodSpeed plugin injects, so both apply to the fork workers.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* bench(memory): pre-size V8 heap geometry in memory bench workers

--no-flush-bytecode alone did not stop the run-to-run flips: the
recurring event is heap-space growth, which allocates several MB at a
run-dependent moment inside the shortened measured windows (error-paths
unmatched vue 674KB vs 2MB, serialization-payload solid resurfacing its
6.4MB attractor on one run in three). Pre-sizing old space and pinning
the semi-space size removes mid-measurement growth while leaving the
per-iteration page map/unmap signal intact - local runs confirm peaks
still track payload sizes exactly (serialization 3.5MB, streaming
30.3MB, levels unchanged).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* bench(memory): size tiny benches just above the 2s measured-run floor

error-paths and server-fn-churn sat at 5-8s measured on CI; fewer
iterations bring them to ~2.3-3.4s, keeping the 2s floor while shrinking
the window a stray allocator event can land in.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* bench(memory): verify the pinned collection against the heap floor

The residual CI flips all share one signature: exactly one iteration's
payload added to the measured peak (serialization-payload vue 3.5 vs
6.9MB, peak-large-page vue 780 vs 1349KB, error-paths redirect vue 300 vs
885KB). On some runners the response teardown holds the payload past the
fixed settle window - released only by a later internal timer - so it
survives the pinned collection and bleeds into the next iteration.

After the fixed 16-turn settle and collection, compare the post-GC heap
against the smallest post-collection size seen this run (the inter-
iteration floor): while it has not returned to the floor, keep hopping
and collecting, bounded at 64 turns. The barrier stays fixed-count in the
common case and extends only in exactly the failure case. Workloads that
genuinely accumulate reachable memory raise the floor as they go, so
accumulation still measures.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* bench(memory): restrict floor verification to peak-shape scenarios

The floor-verified barrier fixed its target - the serialization family
went to <=0.45% across three CI runs, attractor gone - but destabilized
churn/abort scenarios (request-churn solid 420KB vs 3.4MB): their inter-
iteration floor legitimately drifts, so the verification capped out
chronically and the ~48 extra collections per iteration eventually hit a
compaction that double-copies the live set. Split by scenario shape:
serialization-payload, peak-large-page and streaming-peak keep the
verified barrier (flat floor, proven fix); churn and abort scenarios go
back to the plain fixed-count barrier that held them at <=1.7% in the
two previous CI rounds.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-03 21:43:51 +02:00
Flo
208100b7c0
feat(benchmarks): client-side CPU benchmark scenario suite (#7732)
* feat(benchmarks): add client-side CPU benchmark scenario suite

Add 11 client-side CPU benchmark scenarios to benchmarks/client-nav, each
implemented identically across react/solid/vue and tracked by CodSpeed
through the existing Benchmarks workflow (no CI changes needed):

async-pipeline, control-flow, head, history, links, loaders, mount,
nested-params, preload, route-tree-scale, search-params

Each scenario is an isolated file-based-routing app (route trees generated
by @tanstack/router-plugin) built for production and driven in jsdom by a
shared harness (scenarios/harness.ts): circular step sequences of real
<Link> clicks (plus hover/preload/history-traversal/invalidate steps),
each synchronized on the router's onRendered event, with a warm-up lap
that asserts every step's observable output. Determinism rules: no
wall-clock timers (counted 0ms hops only), staleTime/gcTime pinned to 0 or
1e9, deterministic preload staleness, stationary DOM and history depth.

The existing baseline apps and bench names are untouched for CodSpeed
continuity; baseline vite configs only gain an explicit root/setupFiles so
they resolve identically under the new per-framework aggregate configs.

Notable constraints encoded in the scenarios:
- Component-level Await/Suspense is excluded from async-pipeline: React 19
  throttles every Suspense reveal by ~300ms wall-clock, which is
  inherently non-deterministic to benchmark.
- control-flow/react silences React 19's onCaughtError reporting, which
  otherwise dominates the measured loop with console I/O.
- Vue route components must be defined before their createFileRoute call
  (bundled var hoisting silently yields component: undefined otherwise).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* ci: apply automated fixes

* chore(benchmarks): prefix client-nav bench names with "client-"

All benches in @benchmarks/client-nav now start with "client" so they are
easy to identify on the CodSpeed dashboard (the baseline already did).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(benchmarks): address review findings on client-nav scenario stability

Fixes from an adversarial review of the scenario suite:

- mount: create the browser history explicitly and destroy() it on unmount.
  The default per-router createBrowserHistory() monkey-patches
  window.history.pushState/replaceState, chaining one wrapper per router —
  per-mount cost degraded 1.8ms -> 6ms over 3000 mounts (O(N^2) drift in
  the cold-start bench). Verified flat (~1.86ms) after the fix.
- links: replace the five <MatchRoute> components with setup-scoped
  useMatchRoute probes in all three apps. vue-router's MatchRoute calls
  useMatchRoute() inside its render function, leaking one undisposed
  watcher per render — the Vue bench accumulated ~5 dead subscribers per
  navigation. Verified flat per-tick cost over 2000 ticks after the fix.
- all scenarios: bound the scroll-restoration cache with
  getScrollRestorationKey: (location) => location.pathname. The default
  key is a fresh random per-entry location key, so the module-level cache
  grew one entry per push navigation for the whole run.
- harness hover step: dispatch a single mouseover instead of
  mouseover+mouseenter. Solid/Vue attach intent-preload handlers to BOTH
  events, so the old double dispatch ran the preload pipeline twice for
  them but once for React. Verified all three adapters preload exactly
  once per hover via cached-matches probes.
- README: correct the loaders row (the invalidate step means cached routes
  re-run once per lap), the links row, and document the session-history
  growth characteristics.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* feat(benchmarks): cover client rewrites, lazy route chunks, encoded params

Closes the three coverage gaps identified in the scenario-suite analysis:

- new `rewrites` scenario (react/solid/vue): router basepath '/app' composed
  with a locale input/output rewrite pair — the client analog of the SSR
  rewrites scenario. Every href build runs the output rewrite and every
  committed location runs the input rewrite; assertions check both the
  internal router pathname and the external window pathname. The harness
  gained an `initialUrl` option since a basepath app cannot start at '/'.
- route-tree-scale now builds with `autoCodeSplitting: true`, so its
  navigations also exercise lazy route-chunk resolution — the default shape
  of real file-based apps, previously uncovered.
- nested-params and route-tree-scale param sets now include characters that
  need percent-encoding (spaces, `&`, `%`, `+`, unicode) so the segment
  encode/decode paths run on every navigation.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(benchmarks): reduce syscall time in measured loops, lengthen mount bench

CodSpeed excludes syscall time from simulation measures, and past a
threshold it warns ("cannot be consistently instrumented") and skips the
benchmark; the exclusion is also inconsistent run-to-run, which was the
root cause of the two same-code CI swings (route-tree-scale react 13%,
async-pipeline react 3.6%) and of skipped runs on hop-heavy benches like
async-pipeline solid (579 calls / 12.1ms).

- Replace all counted setTimeout(0) hops with setImmediate hops (harness
  timerHop + async-pipeline hopDelay). Both are deterministic event-loop
  turns that yield to timers and the React Node scheduler, but a timer
  costs ~3-4 syscalls (timerfd + epoll) per hop vs ~1 for an immediate.
  Same-machine instrumented before/after: preload solid 39.8ms -> 1.2ms of
  syscall time, preload vue 30.1 -> 1.1, async-pipeline solid 23.5 -> 1.1,
  async-pipeline vue 17.9 -> 0.9. head/route-tree-scale are unchanged
  (their residual syscalls are GC/scheduler, and their measures were
  already stable); history's syscalls come from jsdom's internal
  timer-queued traversal and are not reachable from bench code (its
  measured values are stable regardless).

- mount: 6 ticks per iteration instead of 2. A single mount simulates to
  only ~8ms and very short measures amplify allocator/GC quantization;
  the bench now measures ~50ms+ of simulated CPU.

All 39 benches pass; full nx typecheck green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix(benchmarks): stop history benches sleeping in jsdom's traversal timers

The history benches were skip-warned by CodSpeed for excessive syscall
time (5-26ms, highly variable across runs). Root cause: jsdom delivers
history traversals through two nested window.setTimeout(0) tasks, and Node
clamps zero timers to 1ms of wall time — so while awaiting onRendered
after back/forward/go, the event loop blocked in epoll_wait until each
timer expired. That blocked wall-time is recorded as syscall time, and its
duration depends on host timer behavior, hence the variability.

The harness now reroutes zero-delay window.setTimeout calls onto
setImmediate for the duration of a benchmark (non-zero delays pass
through; clearTimeout handles both). Zero-delay timeouts carry no ordering
semantics a check-phase immediate doesn't satisfy, and the suite's
conventions already forbid real-delay timers in measured code.

Instrumented A/A verification (2 runs per framework): history syscall time
react 23-26ms -> 2.5ms, solid 14-23ms -> 1.1ms, vue 11-12ms -> 1.2ms, with
bit-identical syscall counts across runs and measured values stable to
0.06%. The benches also stopped measuring sleep: locally an iteration
dropped from ~42-49ms to ~5-11ms of actual CPU work. All 39 benches pass.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-07-03 08:18:08 +02:00
github-actions[bot]
0e4f15d741
ci: Version Packages (beta) (#7736) release-2026-07-03-0048 @tanstack/solid-router@2.0.0-beta.23 @tanstack/solid-start-client@2.0.0-beta.23 @tanstack/solid-start-server@2.0.0-beta.23 @tanstack/solid-start@2.0.0-beta.24 2026-07-03 02:44:44 +02:00
Brenley Dueck
f9b0e57ce0
fix(solid-router): resolve defaultNotFoundComponent at render time to avoid hydration desync (#7734)
* fix(solid-router): resolve defaultNotFoundComponent at render time to avoid hydration desync

Previously defaultNotFoundComponent was applied by lazily mutating the
boundary route's options.notFoundComponent when a notFound was handled.
Route objects are module singletons shared across server requests, so
once the server handled any 404, later SSRs of valid URLs wrapped the
match in a CatchNotFound boundary the freshly-hydrating client doesn't
render, shifting hydration keys and leaving the subtree unclaimed
(visible but inert DOM).

Resolve defaultNotFoundComponent at render time in Match.tsx so the
boundary structure is deterministic on both server and client, and add
an e2e regression test.

* ci: apply automated fixes

* chore: add changeset for defaultNotFoundComponent hydration fix

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-07-03 01:47:05 +02:00
Flo
a6337fb98e
bench(memory): stabilize CodSpeed memory benchmarks (#7730)
* bench(memory): stabilize CodSpeed memory benchmarks

Memory flags on PRs were ~85% noise, from two causes:

1. Stale baselines (dominant): the Benchmarks workflow only ran on main
   pushes touching packages/** or benchmarks/**. Main commits outside
   those paths had no CodSpeed run, so PRs were compared against an old
   base run ([^unexpected-base] on every recent codspeed-hq comment; six
   late-June PRs all compared to the same June-23 run). One outlier base
   measurement then replays into every PR until the next eligible push.
   Fix: drop the paths filter for the push trigger + weekly cron backstop.

2. Wall-clock timers racing the single measured run: aborted-requests
   (solid/vue) resolved deferred loader data on 500/750ms timeouts raced
   against abort, and drained cancellation with at most one setTimeout(0);
   streaming-peak staggered deferred sections by milliseconds. Under
   variable runner load and instrumentation slowdown the interleaving —
   and therefore the allocation sequence — differed run to run. Fix:
   count 0ms timers-phase hops (event-loop turns) instead of milliseconds
   everywhere async ordering must be staged, and drain aborts with a
   fixed 8-turn settlement barrier.

Local before/after evidence (8 fresh-process runs per config, CodSpeed V8
determinism flags, idle + CPU-stressed; kernel peak RSS spread):

  aborted-requests/solid idle    11.2MB -> 1.8MB (GC counts bit-identical)
  aborted-requests/solid stress   7.7MB -> 2.5MB
  streaming-peak/solid   idle     6.2MB -> 2.5MB
  request-churn/solid (untouched control): unchanged, confirming harness

streaming-peak/vue keeps ~2% proxy-level variance at any tick count; its
PR flags were the identical -3.2% in all three occurrences, i.e. the
stale-base artifact rather than per-run jitter.

Bench names and workload shapes are unchanged; absolute values will step
once on the CodSpeed dashboard from the removed cross-iteration overlap
(e.g. aborted-requests/solid retained 15.6MB -> 2.5MB per invocation).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* bench(memory): exclude docs/examples/e2e from main benchmark runs, drop cron

paths-ignore instead of no filter: docs/examples/e2e-only pushes cannot
affect benchmark results, and falling back across such a commit is safe
because the previous run's benchmark-relevant code is identical. The
weekly cron backstop is unnecessary for the same reason.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* bench(memory): pin GC between iterations in peak-shape scenarios

A/A runs of the real memory instrument showed the two big-payload peak
scenarios were still unstable with no timers involved: whether V8
collects iteration i's garbage before iteration i+1 allocates its
payload is not reproducible run to run, so the measured peak flipped by
a whole payload (serialization-payload solid: 6.8-9.2 MB across
identical runs; peak-large-page: 3.5-3.7 MB).

Peak scenarios measure the footprint of a single request, not
accumulation, so pin the collection points: settle two event-loop turns
(so trailing renderer/stream teardown is included) and force a GC after
each iteration. Peak then deterministically measures
max(single-request footprint). Churn scenarios are unchanged — their
signal is accumulation, which a forced GC would mask; the README rule
now spells out both sides.

A/A validation (3 identical instrumented runs, solid suite):

  serialization-payload  6.8-9.2 MB  -> 3.5-3.6 MB
  peak-large-page        3.5-3.7 MB  -> 754-757 KB (0.45% spread)
  streaming-peak         38.5-39.5   -> 30.3/30.3/30.3 MB
  churn scenarios        unchanged (aborted-requests 1.4 MB x3)

Absolute values step because cross-iteration garbage no longer inflates
the peak; the new values are the per-request footprint the scenarios
were designed to track.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-07-02 21:44:55 +02:00
github-actions[bot]
ecbbd9a8ec
ci: Version Packages (#7676) @tanstack/react-start-rsc@0.1.26 @tanstack/react-start-server@1.167.21 @tanstack/react-start@1.168.27 @tanstack/router-cli@1.167.18 @tanstack/router-core@1.171.14 @tanstack/router-generator@1.167.18 @tanstack/router-plugin@1.168.19 release-2026-07-01-2138 @tanstack/react-router@1.170.17 @tanstack/react-start-client@1.168.15 @tanstack/router-vite-plugin@1.167.19 @tanstack/solid-router@1.170.17 @tanstack/solid-start-client@1.168.15 @tanstack/solid-start-server@1.167.21 @tanstack/solid-start@1.168.27 @tanstack/start-client-core@1.170.13 @tanstack/start-plugin-core@1.171.19 @tanstack/start-server-core@1.169.16 @tanstack/start-static-server-functions@1.167.18 @tanstack/start-storage-context@1.167.16 @tanstack/vue-router@1.170.16 @tanstack/vue-start-client@1.167.18 @tanstack/vue-start-server@1.167.21 @tanstack/vue-start@1.168.26
ci: changeset release

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-07-01 23:33:19 +02:00
Flo
8bdb21e062
fix(ci): release workflow OOM increase node max-old-space (#7723) 2026-07-01 22:55:47 +02:00
Flo
572fb2b860
fix(ci): release workflow OOM during update-example-deps lockfile update (#7722) 2026-07-01 22:34:33 +02:00
Collin Dillinger
9809a0619d
fix(router-core): preserve percent-encoded URL-unsafe chars in decodeSegment (#7695)
* fix(router-core): preserve percent-encoded URL-unsafe chars in decodeSegment

Replace sanitizePathSegment (which stripped control characters) with a
re-encode step that keeps WHATWG path percent-encode set characters and
control characters in their encoded form after decodeURI.

This preserves the existing decodeURI-based approach which correctly
handles multi-byte UTF-8 sequences, while fixing the mismatch between
the original request URL and the router's internal representation that
caused infinite 307 redirect loops on paths containing these characters.

Fixes #7587.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* ci: apply automated fixes

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Flo <me@florianpellet.com>
2026-06-30 23:27:21 +02:00
github-actions[bot]
ec08c160ca
ci: Version Packages (beta) (#7703) release-2026-06-26-2019 @tanstack/solid-router-ssr-query@2.0.0-beta.24
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-06-26 22:16:02 +02:00
Brenley Dueck
e56bb22fc3
chore: bump @tanstack/solid-query to 6.0.0-beta.5 (#7702) 2026-06-26 16:09:41 +02:00
Flo
bb2daa6952
Reduce postinstall wrangler noise (#7696) 2026-06-25 23:29:10 +02:00
github-actions[bot]
3d265ea439
ci: Version Packages (beta) (#7649) release-2026-06-25-0104 @tanstack/solid-router-devtools@2.0.0-beta.18 @tanstack/solid-router-ssr-query@2.0.0-beta.23 @tanstack/solid-router@2.0.0-beta.22 @tanstack/solid-start-client@2.0.0-beta.22 @tanstack/solid-start-server@2.0.0-beta.22 @tanstack/solid-start@2.0.0-beta.23
ci: changeset release (beta)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-06-25 03:00:11 +02:00
Brenley Dueck
259efbe530
chore: upgrade solid-js to 2.0.0-beta.15 (#7688)
Bump solid-js and @solidjs/web from 2.0.0-beta.14 to 2.0.0-beta.15
across all packages, examples, and e2e apps.

- Pin solid-js as an explicit devDependency in @tanstack/solid-router
  (it previously only declared a floating peer range, so pnpm kept it
  on beta.14).
- Update the scoped vite-plugin-solid babel-preset-solid override to
  beta.15 and add a matching scoped override for @rsbuild/plugin-solid.
- Add minimumReleaseAgeExclude for the freshly published solid betas.
- router-devtools-core intentionally stays on Solid v1.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-25 02:42:21 +02:00
Flo
3d86aee264
pnpm: fix minReleaseAge to 1 day (#7686) 2026-06-24 13:48:04 +02:00
Flo
80d098f5a4
fix pnpm trustPolicy (for good) (#7681) 2026-06-23 22:48:11 +02:00
Flo
d71af0bbcf
add undici 6 to trustPolicyExclude for vite ecosystem ci (#7680) 2026-06-23 21:58:18 +02:00
Flo
7538668f21
ci: bundle-size workdlow outputs its report to stdout (#7677) 2026-06-23 01:19:54 +02:00
Yagiz Nizipli
ba52d2b8f9
perf(start-client-core): zero-copy frame payload extraction (#7662)
extractFlattened() always allocated a new Uint8Array and copied `count`
bytes, even when the requested bytes were fully contained in the first
buffered chunk (the common case, since most frames arrive within a single
network read).

Add a fast path that returns a subarray view of the first chunk when the
bytes are contiguous, avoiding the allocation and the byte copy. The
multi-chunk path is unchanged. The returned view shares the chunk's
backing ArrayBuffer, which is safe because buffered chunks are never
mutated in place after being read.

This is on the hot path for decoding every streamed server-function
response and RawStream binary payload on the client. A micro-benchmark
shows ~3x faster extraction for 1KB frames and ~27x for 64KB frames (the
win scales with payload size).
2026-06-23 00:15:37 +02:00
Flo
279a849916
update better-auth in solid convex example so @noble/ciphers passes trustPolicy (#7656) 2026-06-19 20:08:09 +02:00
Flo
ac821f40aa
docs(start): clarify server functions vs server routes (#7651)
* docs(start): clarify server functions and routes usage

* clean up repetition
2026-06-18 12:49:10 +02:00
Brenley Dueck
51b4bd4f37
perf(solid-router): proxy-free link props in the spread hot path (#7609)
useLinkProps stacked four proxies (merge of defaults, two omit proxies,
and a final merge with the resolved-props memo), and Solid's spread()
re-enumerated them through V8 proxy traps on every navigation for every
Link. Return a plain object with a stable key set instead, with
reactivity in property getters backed by fine-grained memos, and add
href-based equality to the built-location memo.

Client-side navigation benchmark: 7.06ms -> 4.80ms per iteration.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
2026-06-18 03:45:48 +02:00
github-actions[bot]
f23ed0fe73
ci: Version Packages (#7576) release-2026-06-16-2217 @tanstack/react-router@1.170.16 @tanstack/react-start-client@1.168.14 @tanstack/react-start-rsc@0.1.25 @tanstack/react-start-server@1.167.20 @tanstack/react-start@1.168.26 @tanstack/solid-router@1.170.16 @tanstack/solid-start-client@1.168.14 @tanstack/solid-start-server@1.167.20 @tanstack/solid-start@1.168.26 @tanstack/start-plugin-core@1.171.18 @tanstack/start-server-core@1.169.15 @tanstack/vue-start-server@1.167.20 @tanstack/vue-start@1.168.25 2026-06-17 00:12:54 +02:00
Flo
1362bf22d0
ci: pnpm trustPolicy no-downgrade exclude semver@6.3.1 (#7645) 2026-06-16 12:12:14 +02:00
Elecmonkey
e499164c72
feat(start-plugin-core): support Rsbuild preview SSR middleware (#7372)
* fix(start-plugin-core): support rsbuild preview SSR

* fix(start-plugin-core): always install rsbuild SSR middleware in preview

Preview is the only SSR handler in `rsbuild preview`, so gate the opt-out
to dev only and keep the option named `installDevServerMiddleware`.
2026-06-16 10:30:39 +02:00
Flo
734f9072e4
ci: pnpm trustPolicy no-downgrade exclude chokidar@4.0.3 (#7643) 2026-06-16 10:22:04 +02:00
Brenley Dueck
144ddc748e chore: remove unneeded changesets 2026-06-15 07:25:09 -05:00
Flo
a415471437
perf(router-core): cache lightweight route matches (#7601) 2026-06-14 20:56:50 +02:00
Flo
854ac95b0d
benchmark: memory (codspeed) (#7623) 2026-06-14 12:51:10 +02:00
Brenley Dueck
3fe770ad17 fix: update solid ssr benchmark types 2026-06-13 16:32:33 -05:00
autofix-ci[bot]
0747d9b8fa
ci: apply automated fixes 2026-06-13 21:09:57 +00:00
Brenley Dueck
545866dd47 chore: fix tests 2026-06-13 16:07:04 -05:00
Brenley Dueck
1052ab97ba Merge branch 'main' into solid-router-main-merge2 2026-06-13 15:54:31 -05:00
Flo
689c5ab32e
chore(react-router): silence AbortError in renderRouterToStream (#7627) 2026-06-13 19:41:02 +02:00
Flo
36ed57409a
bench: calibrate new ssr benchmarks iteration to reduce variability (#7625)
* bench: calibrate new ssr benchmarks iteration to reduce variability

* better response stream draining

* last remaining fast ssr scenarios
2026-06-13 15:21:57 +02:00
dfedoryshchev
a2b9d51b0a
docs: fix duplicate "to" typos (#7370) 2026-06-12 22:55:18 +02:00
Flo
0c110a934a
ssr benchmarks (#7606) 2026-06-12 22:04:10 +02:00
tsushanth
2215277382
docs(router): drop the broken "LLM Assistance Support" nav entry (#7617) 2026-06-12 21:31:42 +02:00
Tanner Linsley
6f882b7dae
docs(start): rename LLM optimization guide to GEO (#7620) 2026-06-12 11:24:22 -06:00