Overview - Router

router

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
7364
Flaky task→
39a19bcd fix(start-client-core): restore original #tanstack-* import order in hydrateStart.ts Virtual module imports (#tanstack-*) resolve as internal (rank 2), not unknown. They must appear before sibling imports, not after. Reverts mistaken reorder.
by Zelys
Failed
7364
Fix ready→
9a08e6aa fix(start-client-core): restore import order — external type import must follow local type imports
by Zelys
Failed
7364
9a08e6aa fix(start-client-core): restore import order — external type import must follow local type imports
by Zelys
Failed
7364
c4a563d2 fix: reorder imports for ESLint compliance (external before relative)
by Zelys
Canceled
7364
c4a563d2 fix: reorder imports for ESLint compliance (external before relative)
by Zelys
Failed
7364
fe3a3ae0 fix: re-throw redirect and notFound signals in middleware error guards When unwinding middleware, redirect() and notFound() framework signals must be re-thrown to reach the router—they are not Error instances. The previous instanceof Error guard would silently return them as application data, breaking SSR and client-navigation flow detection. Extended both error-handling locations (client fetcher and middleware executor) to also check isRedirect() and isNotFound(), ensuring framework signals propagate correctly while custom error payloads continue to be returned as resolved values.
by Zelys
Failed
7364
Fix ready→
909b9381 fix: handle null returns correctly in server functions The ?? operator treats null as a value, not nullish, so null ?? undefined returns null. However, we need to distinguish between: 1. result.result explicitly set to null (should return null) 2. result.result undefined (should fallback to result.error for custom error payloads) Change to: result.result !== undefined ? result.result : result.error This preserves null while still supporting middleware error payloads. Fixes #7364
by Zelys
Failed
7364
Fix ready→
1abc3487 fix(start-client-core): allow middleware to return custom error structures from catch blocks Middleware that wanted to return structured error responses from catch blocks would have those errors thrown immediately to the client. The middleware protocol was using `.error` property for two incompatible purposes: framework errors (Error instances) and application error data (plain objects). This fix uses JavaScript's type system to distinguish them: only Error instances are thrown, allowing middleware to return custom error structures while preserving proper error propagation for real framework errors. Fixes #7238 BREAKING CHANGE: Middleware that throw non-Error values will now have those values captured in result.error instead of being thrown to the client. Only affects non-standard code patterns; best practice is to throw Error instances.
by Zelys
Failed
7364
e6214af0 fix(start-client-core): allow middleware to return custom error structures from catch blocks Middleware that wanted to return structured error responses from catch blocks would have those errors thrown immediately to the client. The middleware protocol was using `.error` property for two incompatible purposes: framework errors (Error instances) and application error data (plain objects). This fix uses JavaScript's type system to distinguish them: only Error instances are thrown, allowing middleware to return custom error structures while preserving proper error propagation for real framework errors. Fixes #7238 BREAKING CHANGE: Middleware that throw non-Error values will now have those values captured in result.error instead of being thrown to the client. Only affects non-standard code patterns; best practice is to throw Error instances.
by Zelys
Failed
7357
Flaky task→
1674edd8 ci: retrigger CI after Nx Cloud artifact miss
by Zelys
Failed
7357
970370b8 fix(start): import Register from framework package so augmentation works All three framework adapters (react-start, solid-start, vue-start) imported Register from their router package, but the docs tell users to augment their start package. TypeScript module augmentation is module-scoped, so the registered context type was silently ignored. Closes #7353. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
by Zelys
Succeeded
main
afa40ef4 fix(start-server-core): fall back to GET handler for HEAD requests (RFC 9110 §9.3.2) (#7325) Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
by Zelys
Succeeded
7325
97f09f4d fix(start-server-core): guard against undefined ctx.response in HEAD fallback If a fallback GET/ANY handler exits without returning a Response, ctx.response is undefined. Without the guard, handleRedirectResponse passes undefined through and new Response(null, undefined) silently synthesizes a 200 OK, masking the handler bug. Calling throwRouteHandlerError() surfaces the mistake with the same error used everywhere else in the file. Also removes the unsafe cast -- TypeScript narrows the type correctly after the never-returning guard.
by Zelys
Canceled
7325
97f09f4d fix(start-server-core): guard against undefined ctx.response in HEAD fallback If a fallback GET/ANY handler exits without returning a Response, ctx.response is undefined. Without the guard, handleRedirectResponse passes undefined through and new Response(null, undefined) silently synthesizes a 200 OK, masking the handler bug. Calling throwRouteHandlerError() surfaces the mistake with the same error used everywhere else in the file. Also removes the unsafe cast -- TypeScript narrows the type correctly after the never-returning guard.
by Zelys
Canceled
7325
d9d24f02 refactor(start-server-core): use new Response(null, resolved) per reviewer suggestion Adopts the tighter form suggested by @schiller-manuel: passing the resolved Response directly as the ResponseInit arg copies status, statusText, and headers in one shot instead of spreading them manually.
by Zelys