TanStack/router - CodSpeed

router

Blog Docs Changelog

Performance History

Latest Results

perf(router-core): trim SIEVE cache nodes

perf/sieve-cache

1 hour ago

perf(router-core): stop re-validating search params for buildLocation `buildLocation` asked `matchRoutesLightweight` for the current location's accumulated search, which re-ran every matched route's `validateSearch`. `matchRoutesInternal` already computes that exact value, so it now stamps it on the location it resolved (`_search`) and `matchRoutesLightweight` reads it back. The value is therefore correct by construction - it was computed for that very location object - and the validator loop is only reached for a location that was never matched, such as a freshly built destination. That removes one full validation pass per navigation, three runs per matched route down to two. In the same block, `matchRoutesInternal` now hands the validator the object that becomes the match's search and fills it in place, so a branch allocates one search object per depth instead of three. Measured with zod v4 schemas on a 3-route branch (jsdom, 3000 navigations): 9 -> 6 `validateSearch` calls per navigation, ~73-77us -> ~64-68us. Bundle: react-router.minimal 85807 -> 85827 gzip (+20), react-router.full 89391 -> 89411 gzip (+20). The in-place fill is byte-neutral on its own (+0/+1); the stamp-and-reuse accounts for the whole +20. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C1tX2n8xegVBsZqoJPu7iv

perf/single-search-validation-lean

4 hours ago

perf(router-core): replace the LRU cache with a trimmed SIEVE cache The hand-rolled doubly-linked LRU relinked the hit entry to the newest position on every `get`. Every cache in the router (resolvePathCache, the route tree's matchCache/singleCache/flatCache, the SSR manifest cache) is hit-dominated: a page of links re-resolves the same handful of paths on every navigation, so the relink was pure overhead. SIEVE (https://cachemon.github.io/SIEVE-website/) keeps a FIFO list and a visited bit per entry; a hit only sets the bit, and eviction sweeps a hand from the oldest entry, clearing bits and dropping the first unvisited one. Same API as before (`get`/`set`/`clear`, fixed `max`), no dependency, and the old implementation's stale-`oldest` eviction edge case is gone. Microbenchmark (ns/op, Node 25): get-hit 17.0 -> 13.9, set-insert 64.9 -> 50.8, set-evict 79.9 -> 79.9, scan-then-return 41.0 -> 34.8, get-miss 16.2 -> 19.3. Hit ratios on the links and route-tree-scale client-nav traces are identical (working sets of 3-9 keys never evict). Bundle gzip: react-router.minimal -8 B, react-router.full -15 B. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C1tX2n8xegVBsZqoJPu7iv

perf/sieve-cache

4 hours ago

test(router-core): pin that a partial `params` object still inherits A plain `params` object does not have to be complete: `resolveNextParams` merges it over the current location's params, so `<Link to="/posts/$postId/edit" params={{}}>` or `params={{ tab: 'x' }}` under `/posts/$postId` still take `postId` from wherever the user currently is. Treating every plain object as self-sufficient — dropping the `usedParams` check in `buildLocation` and setting the memo's "reads the current location" bit only when `params` is not a plain object — would memoize these links and freeze their href at the value it had when they mounted. This test fails that way (`/posts/1/edit` instead of `/posts/2/edit`) and passes with the check. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C1tX2n8xegVBsZqoJPu7iv

perf/link-deps-lean

4 hours ago

perf(router-core): share settle chain between superseded navigation waiters (#8222) perf(router-core): make superseded navigation waiters share one settle chain `awaitCurrent` looped `await current.done` and re-read `router._tx` after each completion. Under back-to-back navigations (anything that starts the next navigation in the same tick as `onRendered`, including the client-nav benchmarks) every superseded waiter woke on every successor, so a burst of N navigations cost N²/2 microtask iterations and kept every superseded transaction alive until the router went idle. Each transaction's `done` promise now follows its current successor, so every waiter on a transaction shares the same chain instead of polling successors independently. A waiter still resolves once the router has settled on a transaction other than its owner. Measured in benchmarks/client-nav (react, navigations per 10s, jsdom): baseline 15.4K -> 43K, route-tree-scale 17.9K -> 98K, search-params 16.5K -> 55K. The instrumented baseline run showed 125.8M loop iterations for 15,867 navigations before the change. Bundle: react-router.minimal -1 B gzip vs main. Claude-Session: https://claude.ai/code/session_01C1tX2n8xegVBsZqoJPu7iv Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

main

4 hours ago

perf(router-core): make superseded navigation waiters share one settle chain `awaitCurrent` looped `await current.done` and re-read `router._tx` after each completion. Under back-to-back navigations (anything that starts the next navigation in the same tick as `onRendered`, including the client-nav benchmarks) every superseded waiter woke on every successor, so a burst of N navigations cost N²/2 microtask iterations and kept every superseded transaction alive until the router went idle. Each transaction's `done` promise now follows its current successor, so every waiter on a transaction shares the same chain instead of polling successors independently. A waiter still resolves once the router has settled on a transaction other than its owner. Measured in benchmarks/client-nav (react, navigations per 10s, jsdom): baseline 15.4K -> 43K, route-tree-scale 17.9K -> 98K, search-params 16.5K -> 55K. The instrumented baseline run showed 125.8M loop iterations for 15,867 navigations before the change. Bundle: react-router.minimal -1 B gzip vs main. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C1tX2n8xegVBsZqoJPu7iv

fix/await-current-shared-settle

5 hours ago

bench(ssr): channel-aware dehydration markers The SSR scenarios asserted the $_TSR bootstrap to locate the dehydration payload in rendered HTML; Solid's channel now emits __TSR_P records instead. findDehydrationMarkerIndex accepts either marker so the benchmarks stay meaningful across both channels. Co-authored-by: Cursor <cursoragent@cursor.com>

ryansolid:feat/solid-ssr-transport-payload

15 hours ago

fix(solid): unbreak CI after the solid-js rc.6 bump Two things were failing the Test job: - @tanstack/solid-router test:eslint: the repro-external-ssr harness is not part of the package tsconfig, so the typed parser rejected its .tsx files. Ignore the harness in the package eslint config; it is a standalone vite script, not shipped code. - Four example builds (basic-solid-query, basic-solid-query-file-based, kitchen-sink-file-based, kitchen-sink-solid-query) run tsc, and the rc.6 types no longer accept the one-argument createEffect form. Convert the eleven call sites to the two-argument createEffect(source, effect) form already used by the sibling examples and e2e apps. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

ryansolid:feat/solid-native-ssr-transfer

18 hours ago

Latest Branches

+4%

perf(router-core): replace the LRU cache with a trimmed SIEVE cache#8230

1 hour ago

a2750b8

perf/sieve-cache

0%

perf(router-core): stop re-validating search params for buildLocation#8231

6 hours ago

63b3cfb

perf/single-search-validation-lean

+11%

perf(router-core,react-router): reuse a Link's built location when it reads none of the current one#8229

5 hours ago

d670994

perf/link-deps-lean

© 2026 CodSpeed Technology

Home Terms Privacy Docs