Run details

routerWorkspace

CI Pipeline Executions
- Current executionSucceeded
  schiller-manuel-lazy-current-match-layer
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

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>

nx run-many --target=build --exclude=examples/** --exclude=e2e/**

Succeeded

4 CPU cores

d26a07c88406

14%

Cache hits

6 of 43 tasks used cache.

Get faster results

Learn how to enable distribution.

Atomizer enabled

43 groups of tasks optimized.

© 2026 - Nx Cloud

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

routerWorkspace