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

6,533 commits

Author SHA1 Message Date
github-actions[bot]
704145c6d5
ci: Version Packages (#7946) release-2026-08-04-2036 @tanstack/react-router-devtools@1.167.1 @tanstack/react-router@1.170.19 @tanstack/react-start-client@1.168.17 @tanstack/react-start-rsc@0.1.35 @tanstack/react-start-server@1.167.24 @tanstack/react-start@1.168.36 @tanstack/router-cli@1.167.22 @tanstack/router-core@1.171.16 @tanstack/router-devtools-core@1.168.1 @tanstack/router-devtools@1.167.1 @tanstack/router-generator@1.167.22 @tanstack/router-plugin@1.168.24 @tanstack/router-vite-plugin@1.167.24 @tanstack/solid-router-devtools@1.167.1 @tanstack/solid-router@1.170.19 @tanstack/solid-start-client@1.168.17 @tanstack/solid-start-server@1.167.24 @tanstack/solid-start@1.168.35 @tanstack/start-client-core@1.170.15 @tanstack/start-plugin-core@1.171.27 @tanstack/start-server-core@1.169.19 @tanstack/start-static-server-functions@1.167.20 @tanstack/start-storage-context@1.167.18 @tanstack/vue-router-devtools@1.167.1 @tanstack/vue-router@1.170.18 @tanstack/vue-start-client@1.167.20 @tanstack/vue-start-server@1.167.24 @tanstack/vue-start@1.168.34
ci: changeset release

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-08-04 22:25:17 +02:00
Flo
3740f44786
docs: align loader docs with lane rewrite (#7949)
* docs: align loader docs with lane rewrite

* docs: refine lane loader documentation

* docs: expand link preloading guide
2026-08-04 22:23:02 +02:00
Flo
a4942ff68a
fix(router): correct lane loader changeset (#7948)
* fix(router): correct lane loader changeset

* fix(router): keep lane loader release patch

* docs(router): clarify removed internal stores
2026-08-04 21:19:20 +02:00
Flo
45c4ad8d62
fix(router-core): lane match loader rewrite (#7805)
* fix: lane match loader rewrite

---------

Co-authored-by: Manuel Schiller <6340397+schiller-manuel@users.noreply.github.com>
2026-08-04 20:28:11 +02:00
github-actions[bot]
65ae78cf06
ci: Version Packages (#7945) release-2026-08-03-2216 @tanstack/react-start-rsc@0.1.34 @tanstack/react-start-server@1.167.23 @tanstack/react-start@1.168.35 @tanstack/solid-start-server@1.167.23 @tanstack/solid-start@1.168.34 @tanstack/start-plugin-core@1.171.26 @tanstack/start-server-core@1.169.18 @tanstack/vue-start-server@1.167.23 @tanstack/vue-start@1.168.33
ci: changeset release

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-08-04 00:09:59 +02:00
Ahmed Sabry
10dc3f63e6
docs: version optional param to only capture version not capturing "e… (#7932)
* docs: version optional param to only capture version not capturing "extra" as version

* fix: close template literal
2026-08-04 00:04:26 +02:00
Manuel Schiller
65f7b7f791
fix(start): keep server-only routes out of RSC bundles (#7944)
Use the Start storage context for request cancellation and focused server entrypoints to keep unrelated route dependencies out of the RSC module graph. Add emitted-build regression coverage for the boundary.

fixes #7938
2026-08-04 00:02:37 +02:00
Alem Tuzlak
b5e540d74a
docs: use the dynamic README header endpoint (#7940)
* docs: use the dynamic README header endpoint

* docs: add README header banners to the framework adapter packages
2026-08-03 21:03:29 +02:00
Ahmed Sabry
2cb221cfd3
Fix typo in path-params documentation (#7931) 2026-08-01 14:15:16 +02:00
Nicolas Beaussart
03699c4c02
chore(ci): improve Nx sandbox cache declarations (#7833)
* chore(ci): establish CI timing baseline

* faster maybe ?

* chore(ci): declare sandbox task inputs and outputs

* chore(ci): declare remaining build sandbox inputs

* another batch

* try fixing e2e import protection

* more sandbox fixes

* fix(e2e): isolate import protection artifacts

* fix script

* fix import protection

* tune even more

* tune even more with some global ignore

* ok, anohter try

* fix(ci): avoid reading captured build logs

* one last improvement for tonight
2026-08-01 13:39:33 +02:00
github-actions[bot]
8212950807
ci: Version Packages (#7927) release-2026-07-30-2211 @tanstack/vue-start@1.168.32 @tanstack/react-start-rsc@0.1.33 @tanstack/react-start@1.168.34 @tanstack/solid-start@1.168.33 @tanstack/start-plugin-core@1.171.25
ci: changeset release

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2026-07-31 00:04:54 +02:00
Cong-Cong Pan
7592555b86
fix(start): align Rsbuild SSR asset URLs for css?url imports (#7590)
* fix(start): align Rsbuild SSR asset URLs for css?url imports

* rm vite-env.d.tst

* ci: apply automated fixes

* fix: ts type

* ci: apply automated fixes

* ci: apply automated fixes (attempt 2/3)

* fix: docs code

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-07-30 23:30:40 +02:00
Bhavesh Desale
77ed6d5c3a
fix(eslint-plugin-start): support ESLint 10 peer dependency (#7924) 2026-07-30 22:42:20 +02:00
github-actions[bot]
a3ee355b59
ci: Version Packages (#7903) release-2026-07-29-2018 @tanstack/react-start-rsc@0.1.32 @tanstack/react-start@1.168.33 2026-07-29 22:14:03 +02:00
Cong-Cong Pan
f04ddc61e7
fix(start): skip errored Rspack modules during import protection (#7685)
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-07-29 21:11:16 +02:00
Tanner Linsley
179d9b9b5e
Improve Router and Start agent skills (#7867)
* docs: improve Router and Start agent skills

* docs: address agent skill review feedback

* ci: apply automated fixes

* docs: align agent skills with intent schema

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-07-26 10:53:49 -06:00
Sreetam Das
fc83c0383f
fix(react-start-rsc): require @vitejs/plugin-rsc >=0.5.30 for route component HMR (#7900) 2026-07-26 01:12:08 +02:00
Manuel Schiller
88f366ab8e
chore: migrate to typescript 7 (#7887) 2026-07-23 23:10:51 +02:00
Flo
3a5575627d
test: add regression coverage for existing router behavior (#7886) 2026-07-23 22:13:21 +02:00
Sarah Gerrard
a76c192f1c
docs: Update Guides section and add back in missing pages (#7864) 2026-07-22 22:13:55 +02:00
Sajad Torkamani
2b08d9ba4b
docs: minor docs improvements (#7842) 2026-07-22 22:12:34 +02:00
Cong-Cong Pan
21a8597952
chore: add React Start basic Rsbuild example (#7729)
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
2026-07-22 22:09:03 +02:00
Zakher Masri
07ce90304d
docs: remove stray semicolon in i18n page (#7870)
fix: remove stray semicolon
2026-07-21 11:45:50 -07:00
Manuel Schiller
edf55759d8
ci: omit unchanged bundle size scenarios (#7856) 2026-07-19 22:34:06 +02:00
github-actions[bot]
49bd9fa447
ci: Version Packages (#7857) release-2026-07-19-1434 @tanstack/react-start-rsc@0.1.31 @tanstack/react-start@1.168.32 @tanstack/router-plugin@1.168.23 @tanstack/router-vite-plugin@1.167.23 @tanstack/solid-start@1.168.32 @tanstack/start-plugin-core@1.171.24 @tanstack/vue-start@1.168.31 2026-07-19 16:29:16 +02:00
Manuel Schiller
49f6863245
fix(router-plugin): preserve HMR state for lowercase split components (#7855) 2026-07-19 12:09:25 +02:00
Manuel Schiller
218eab2c3b
chore: regenerate route trees (#7853) 2026-07-19 09:20:56 +02:00
github-actions[bot]
ecb1ef4817
ci: Version Packages (#7854) release-2026-07-19-0715 @tanstack/react-start-rsc@0.1.30 @tanstack/react-start@1.168.31 @tanstack/solid-start@1.168.31 @tanstack/start-plugin-core@1.171.23 @tanstack/vue-start@1.168.30 2026-07-19 09:11:05 +02:00
Manuel Schiller
ffdd64e842
fix(start): preserve resolved virtual module ids (#7844) 2026-07-18 20:08:42 +02:00
Alex Kostyniuk
31a634d84e
docs: update Next.js middleware description (#6155)
* docs: update Next.js middleware description

* Fix grammar in Next.js Edge Runtime description

Correct grammatical error in comparison of Next.js limitations.

* Revise Next.js proxy.ts runtime details

Updated Next.js proxy.ts description to reflect runtime changes.

* removed the not needed '+'

---------

Co-authored-by: Sarah Gerrard <hello@sarahgerrard.me>
2026-07-17 18:19:11 -07:00
github-actions[bot]
62a191baa0
ci: Version Packages (#7846) release-2026-07-18-0030 @tanstack/react-start-rsc@0.1.29 @tanstack/react-start@1.168.30 @tanstack/router-cli@1.167.21 @tanstack/router-generator@1.167.21 @tanstack/router-plugin@1.168.22 @tanstack/router-vite-plugin@1.167.22 @tanstack/solid-start@1.168.30 @tanstack/start-plugin-core@1.171.22 @tanstack/vue-start@1.168.29 2026-07-18 02:25:47 +02:00
Manuel Schiller
78dd1a645d
fix(router-generator): preserve dots in virtual routes (#7845) 2026-07-18 01:17:42 +02:00
Sarah Gerrard
85ef32ad7b
docs: refresh contribution guidelines (#7839) 2026-07-18 00:48:35 +02:00
github-actions[bot]
604996d14c
ci: Version Packages (#7841) release-2026-07-17-2231 @tanstack/react-start-rsc@0.1.28 @tanstack/react-start@1.168.29 @tanstack/router-cli@1.167.20 @tanstack/router-generator@1.167.20 @tanstack/router-plugin@1.168.21 @tanstack/router-vite-plugin@1.167.21 @tanstack/solid-start@1.168.29 @tanstack/start-plugin-core@1.171.21 @tanstack/vue-start@1.168.28 2026-07-18 00:25:19 +02:00
Thijs Koerselman
e56a67742d
fix(router-generator): make buildRouteTree route ordering deterministic (#7751)
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Manuel Schiller <6340397+schiller-manuel@users.noreply.github.com>
2026-07-17 23:01:54 +02:00
Sajad Torkamani
6184661e56
docs: small improvements to wording (#7840) 2026-07-17 21:40:35 +02:00
Mohamed Yahye El Joud
00d00b3155
docs: Update environment variable validation to use z.url() (#5570) 2026-07-17 20:47:19 +02:00
maurer2
d3e1cf4e2f
Add direction-aware view transitions to view transitions example repo (#5791)
* Add direction aware view transitions

* Restore comment

* Linter fix

---------

Co-authored-by: Birk Skyum <74932975+birkskyum@users.noreply.github.com>
2026-07-17 16:19:58 +02:00
Flo
0b178a79e2
test: add more regression coverage for existing router behavior (#7822) 2026-07-15 09:48:19 +02:00
Flo
11a6a0d8ba
test: add regression coverage for existing router behavior (#7812) 2026-07-14 01:44:02 +02:00
Pierre-Luc Auclair
a41f26547c
chore(deps): bump @playwright/test to ^1.61.0 across the workspace (#7772) 2026-07-14 00:06:59 +02:00
Florian Fehrenbacher
4d4171fdda
fix: use relative path for srvx static files (#7799) 2026-07-13 23:38:26 +02:00
github-actions[bot]
58c005fcb1
ci: Version Packages (#7811) release-2026-07-13-2136 @tanstack/react-router@1.170.18 @tanstack/react-start-client@1.168.16 @tanstack/react-start-rsc@0.1.27 @tanstack/react-start-server@1.167.22 @tanstack/react-start@1.168.28 @tanstack/router-cli@1.167.19 @tanstack/router-core@1.171.15 @tanstack/router-generator@1.167.19 @tanstack/router-plugin@1.168.20 @tanstack/router-vite-plugin@1.167.20 @tanstack/solid-router@1.170.18 @tanstack/solid-start-client@1.168.16 @tanstack/solid-start-server@1.167.22 @tanstack/solid-start@1.168.28 @tanstack/start-client-core@1.170.14 @tanstack/start-plugin-core@1.171.20 @tanstack/start-server-core@1.169.17 @tanstack/start-static-server-functions@1.167.19 @tanstack/start-storage-context@1.167.17 @tanstack/vue-router@1.170.17 @tanstack/vue-start-client@1.167.19 @tanstack/vue-start-server@1.167.22 @tanstack/vue-start@1.168.27 2026-07-13 23:31:08 +02:00
Manuel Schiller
caebc57045
fix deps (#7810) 2026-07-13 23:10:34 +02:00
Manuel Schiller
e2dd2049cb
fix(router-core): handle window and element scroll restoration independently (#7807) 2026-07-13 21:45:55 +02:00
Manuel Schiller
e65f0c84c1
fix deps in example (#7809) 2026-07-13 21:44:44 +02:00
Soheil Nikroo
41f7bf3283
Update README for WorkOS example: change WORKOS_REDIRECT_URI to point… (#7802)
Update README for WorkOS example: change WORKOS_REDIRECT_URI to point to /api/auth/callback
2026-07-12 06:31:18 -07: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