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

12m 52s

167 CI pipeline executions

Computation time saved

44d 9h

Cache hit rate

46%

Time to Green

1h 6s

Was 2h 28m, improved by 60%

Failed
8574
bd367403 fix(solid-router): record observe redirect hops the way Solid Router folds them A navigation sent elsewhere while pending (a `beforeLoad` or loader redirecting it, or a second navigation requested before the first published) left one record naming only the final destination: no `redirects`, nothing of where it had been headed. Solid Router declares each location write, and a write while the previous navigation is still pending (held, or not yet in history) is a hop of it, `redirect: n` (`navigationDepth`): the engine folds it onto the pending record, which keeps the user's request time and interaction, moves its destination, and keeps the abandoned one in `redirects`. That includes a second click while the first is pending, so the first click's interaction winning is Solid Router's semantics too, not an adapter artifact. The browser moving (popstate) is written with `_navigation: -1`, not a hop: a navigation of its own that supersedes the pending one. The Transitioner now tracks where a pending request is headed; a push or replace before it publishes records a hop (the destination left, and when it was sent on). The publish that lands is wrapped in the request's ref with a nested `redirect: n` ref per hop, which is the shape Solid Router's writes produce. A back/forward while pending starts a new request. Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Cursor <cursoragent@cursor.com>
by Ryan Carniato
R