Run details

routerWorkspace

CI Pipeline Executions
- Current executionSucceeded
  perf/hydrate-without-awaiting-component-chunks
- Runs and Agents
- TimelineBeta
- Configuration
- Self-Healing CI
- Project Graph
- Circular DependenciesEnterprise
- Resource Usage
- Analysis
- ConformanceEnterprise
Runs

Insights

Compare tasks
Analytics

perf(router-core): hydrate without awaiting code-split component chunks hydrate() awaited loadRouteChunk() for every committed match before setMatches, so a React root committed nothing, not even chrome from the entry chunk, until the page's whole component closure had downloaded. React keeps a dehydrated Suspense boundary's server HTML while a lazyRouteComponent suspends, so the React Router now sets _hydrateWithoutComponentChunks and hydrate() only starts those loads. A lane with unmerged lazyFn options still waits, because such a route has no component yet and would render <Outlet /> in its place. Solid and Vue do not set the flag and keep the previous behavior. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

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

Succeeded

4 CPU cores

read access token used

ca1ce8308484

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