Overview - Router

routerWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

router

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools

routerWorkspace

Average execution time

14m

128 CI pipeline executions

Computation time saved

19d 11h

Cache hit rate

39%

Time to Green

2h 27s

Was 4h 21m, improved by 54%

Succeeded
8406
1f197adf perf(router-core): match the current location lazily in buildLocation `buildLocation` matched the current location up front for every build, although the result is only read by relative destinations, inherited params, `search: true` or updater functions and search middlewares. An absolute destination with its params given, on a branch without search middlewares, never reads it, yet still paid three store reads and a WeakMap lookup per call. The match is now computed on first read, and the destination template is scanned for `$` once instead of twice. Server `buildLocation` of `/items/$itemId` with params on a middleware-free tree: 399 -> 382 ns per call (-4%). Builds that read the current match are unchanged. react-router.minimal gzip +4 (86008 -> 86012, the stack base). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
by Manuel Sch...
M
Succeeded
8406
4e935850 perf(router-core): match the current location lazily in buildLocation `buildLocation` matched the current location up front for every build, although the result is only read by relative destinations, inherited params, `search: true` or updater functions and search middlewares. An absolute destination with its params given, on a branch without search middlewares, never reads it, yet still paid three store reads and a WeakMap lookup per call. The match is now computed on first read, and the destination template is scanned for `$` once instead of twice. Server `buildLocation` of `/items/$itemId` with params on a middleware-free tree: 399 -> 382 ns per call (-4%). Builds that read the current match are unchanged. react-router.minimal gzip +4 (86008 -> 86012, the stack base). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
by Manuel Sch...
M
Succeeded
schiller-manuel-lazy-current-match-layer
9eb460f5 perf(router-core): match the current location lazily in buildLocation `buildLocation` matched the current location up front for every build, although the result is only read by relative destinations, inherited params, `search: true` or updater functions and search middlewares. An absolute destination with its params given, on a branch without search middlewares, never reads it, yet still paid three store reads and a WeakMap lookup per call. The match is now computed on first read, and the destination template is scanned for `$` once instead of twice. Server `buildLocation` of `/items/$itemId` with params on a middleware-free tree: 399 -> 382 ns per call (-4%). Builds that read the current match are unchanged. react-router.minimal gzip +4 (86008 -> 86012, the stack base). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
by Manuel Sch...