taTanStack
GitHubrouterWorkspace
GitHub
  • 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
    • Current runSucceeded
    • Tasks
    • Resource Usage
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 affected --targets=test:eslint,test:unit,test:e2e,test:types,test:build,build --parallel=3
Succeeded
read access token used
ca1ce8308484
5%

Cache hits

41 of 797 tasks used cache.

92%

Distribution saved time

13m 07s instead of 2h 45m 33s.

Atomizer enabled

312 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubrouterWorkspace