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

175 CI pipeline executions

Computation time saved

41d 57m

Cache hit rate

50%

Time to Green

1h 27m

Was 2h 34m, improved by 43%

Succeeded
8637
449e8183 fix(start): handle params.parse failures before server route handlers Since #8434, server route handlers receive parsed params, but a params.parse failure escaped the handler pipeline. A thrown notFound() became a 500, and a page route whose handler would have deferred to rendering could no longer render its not-found page. A thrown notFound() from a handler or from params.parse now responds 404 unless middleware handles it. When params.parse throws on a route with a component and the request explicitly accepts text/html, the handler is skipped and the app router renders the page, as it would without a handler. Refs #8431 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
by Sheraff