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
Succeeded
7428
d8feafbd refactor(start): narrow request-context fix to default-entry Register import Fixing the augmented `server.requestContext` typing only needs the default-entry `ServerEntry` to import `Register` from the framework start package (the module users augment), not the router package. Module augmentation flows only when the consuming type imports `Register` from the same specifier and that module is in the type graph. Revert the broader, unnecessary churn back to main: - start-server-core: request-handler, createStartHandler, request-response signatures (RequestHandler/RequestOptions/RequestHandlerParameters) - e2e react-start import-protection test - changeset: drop start-client-core/start-server-core (now unchanged) Verified against built packages: e2e react/solid/vue basic `tsc --noEmit` pass; wrong context value and missing required context are rejected; start-client-core/start-server-core test:types pass.
by SeanCassiere
Succeeded
7428
714d5e2e test(e2e): update type-only request handler import
by SeanCassiere
Canceled
7428
714d5e2e test(e2e): update type-only request handler import
by SeanCassiere
Failed
7428
Fix ready→
d6b06351 chore: add changeset
by SeanCassiere
Succeeded
7428
89310e05 chore(e2e,examples): regenerate route trees for start
by SeanCassiere
Failed
7428
d3a6b503 revert: docs(start): use router package for module declaration to type the request context (#7427) This reverts commit 2506478fa81f8603eb69d7ce4b17d3280dececfb since these changes now can infer the types off of Start's Register interface
by SeanCassiere
Failed
7428
d3a6b503 revert: docs(start): use router package for module declaration to type the request context (#7427) This reverts commit 2506478fa81f8603eb69d7ce4b17d3280dececfb since these changes now can infer the types off of Start's Register interface
by SeanCassiere
Succeeded
7427
0d22ccd2 docs(start): use router package for module declaration to type the request context
by SeanCassiere
Succeeded
7258
a6f58c2c chore(examples): runtime enforce for needing the `VITE_CONVEX_URL`
by SeanCassiere
Succeeded
7258
7d639ded chore(examples): runtime enforce for needing the `VITE_CONVEX_URL`
by SeanCassiere
Failed
7258
Flaky task→
f502013d refactor(start-client-core): use a more explicit typing to `CustomFetch` type
by SeanCassiere
Succeeded
7258
b9344eca refactor(start-client-core): use a more explicit typing to `CustomFetch` type
by SeanCassiere
Failed
7258
2173dc7a refactor(router-plugin): upgrade unplugin to `v3`
by SeanCassiere
Succeeded
7257
69e3ecd4 chore: checkin outdated route-tree files for react and solid examples
by SeanCassiere
Canceled
6920
543d4cb4 chore: add changeset
by SeanCassiere
Succeeded
main
773c7c9c chore: generate route-tree for all sandboxes a recent change to generator, meant that all the sandboxes had their route-trees files being out-of-date
by SeanCassiere