Overview - Router

routerWorkspace

CI Pipeline Executions
- Filtered
Runs
Demo

Insights

Compare tasks
Analytics

Overview

router

Loading workspace stats

Loading workspace insights...

Statistics interval

7 days30 days

Latest CI Pipeline Executions

Filter

Fuzzy

Sort by

© 2026 - Nx Cloud

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

routerWorkspace

Average execution time

10m 50s

158 CI pipeline executions

Computation time saved

14d 16h

Cache hit rate

30%

Time to Green

35m 32s

Was 1h 59m, improved by 70%

Succeeded
8472
dc59eb9d test(react-router): use fake timers for pending-min hold assertion Drive the painted hold test with a controlled clock instead of a real sleep so a delayed event loop cannot expire the minimum window before the hold assertion runs.
by Gianmarco ...
G
Failed
8472
Fix ready→
a0fc7c08 fix(router-core): advance the pending boundary past settled matches A load transaction presents one snapshot with a single match forced to pending, and it offered any match outside the retained prefix as that boundary before the match settled, whether or not the route had a loader. It then treated every presented match with a pending status as the painted boundary, but only the first one is on screen, because the fallback replaces the rest of the subtree. Together those made a settled ancestor keep selecting itself as the boundary and stop early on its own session, so the presented snapshot froze until the slowest loader in the branch resolved. Navigating between sibling layouts replaced the whole shell, including a layout that had nothing left to load. The painted boundary is now the first presented pending entry, and a settled match no longer takes the boundary, so a layout route with no loader renders as soon as it settles and the fallback stays on the match that is still loading. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
by Gianmarco ...
G