Overview - Router

router

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
7519
Environment issue→
fb72d535 fix(start): resolve server requestContext type for global middleware The server `Register` augmentation (`server.requestContext`) was not seen by `createMiddleware().server` context nor by `handler.fetch`, leaving `context` typed as `undefined`/`BaseContext`. The default server entry typed `handler.fetch` via `RequestHandler<Register>` with `Register` from `@tanstack/{react,solid}-router`. Once an app augments the router's `Register` (e.g. the universal `router` registration in router.tsx), that interface becomes a separately-merged declaration that no longer sees the start `server.requestContext` augmentation. Read `Register` from `@tanstack/{react,solid}-start` instead so the handler context aligns with the registered context and the server middleware chain. Also align docs to augment `@tanstack/react-start` (matching the generated route-tree footer) and add an e2e repro. Co-authored-by: opencode <noreply@opencode.ai>
by SeanCassiere