Run details

routerWorkspace

CI Pipeline Executions
- Current executionSucceeded
  fix/server-route-params-parse-failure
- 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

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>

nx run-many --target=build --exclude=examples/** --exclude=e2e/**

Succeeded

4 CPU cores

read access token used

d752d1698637

Get faster results

Learn how to enable distribution.

Atomizer enabled

43 groups of tasks optimized.

Resource usage reports are turned off for this workspace

Your organization has the Resource usage add-on, but this workspace does not collect metrics for non distributed runs. Turn it back on in workspace settings.

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

routerWorkspace