Run details

routerWorkspace

CI Pipeline Executions
- Current executionSucceeded
  perf/single-search-validation-lean
- Runs and Agents
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

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

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

Succeeded

4 CPU cores

read access token used

cd4d01c28231

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