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

13m 22s

195 CI pipeline executions

Computation time saved

24d 6h

Cache hit rate

40%

Time to Green

1h 35m

Was 3h 48m, improved by 58%

Succeeded
8461
49cc3b6a test(solid-start): expect both flight sources on the single-flight request The router now registers as the unnamed flight-data consumer, so the transport advertises it on the request leg under the reserved id "true" next to Start's "tsr". The response still folds only "tsr". Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
by Brenley Dueck
B
Failed
8461
Fix ready→
ee8fc8e0 feat(solid-router): consume server-function response metadata RouterContextProvider registers the router as the unnamed single-flight consumer of Solid's server-function transport on the client, so the response helpers a mutation returns take effect without the caller wrapping the call. redirect(): the carrier delivers an absolute target, so the soft/hard split is a real origin comparison — same-origin navigates under the router with replace (the destination takes the submission's place in history), any other origin goes through navigate({ href }) so the document reload still passes the protocol allowlist and blockers. Route data: any declaration of a write — redirect(), reload({ revalidate }), respond(value, { revalidate }), the reserved '*' — reloads through router.invalidate(). An empty declaration (revalidate: []) is honored as nothing to reload. Navigation runs before invalidation so a redirect costs one load: invalidate's load already reads the destination as the latest location, and the adapter's follow-up load adopts those loader flights rather than restarting them, so the destination commits with shared layouts reloaded and the abandoned page never reruns its own loaders (the other order does). X-Revalidate keys name entries in caches the router does not own and are left to those caches' consumers. Co-authored-by: Claude via Cursor <noreply@cursor.com> Co-authored-by: Cursor <cursoragent@cursor.com>
by Ryan Carniato
R