Run details

routerWorkspace

CI Pipeline Executions
- Current executionSucceeded
  codex/fewer-store-updates
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

perf(router-core): publish fewer store updates during navigation Every synchronous frame between two beforeLoad awaits now publishes as one store update: `contextualize` settles each hook inside `router.batch`, so ending a beforeLoad and starting the next hook or the loaders no longer produces separate `isFetching` publications. Loader starts for a whole lane publish together, and a superseding navigation clears the previous lane's presented fetching state in the same update that publishes its new location. `waitFor` resolves plain values without registering an abort listener. Store updates in the full navigation case drop from 7 to 6 (React), 6 to 5 (Solid, Vue). Deterministic publication-sequence tests explain every remaining update (no fallback, fallback during beforeLoad, fallback during the loader, ready before pendingMinMs, replacement while the fallback is visible, superseding navigation) and assert that persistent useSearch/useParams consumers and whole-state consumers only re-render when their selection changes. A focused fan-out benchmark and a core regression for a store subscriber that navigates during the start flush are added. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> (cherry picked from commit b3614be185661383d60bdff9f53aeadfa056fe83)

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

Succeeded

4 CPU cores

read access token used

33e0ced28416

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