TanStack
OSS
router
Sign in / Sign up
Open main menu
router
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
main
426c2b54 fix: pass pathname to global request middleware in createStartHandler (#6648) * fix: pass pathname to global request middleware in createStartHandler The two `executeMiddleware` calls for global request middleware in `createStartHandler` were missing the `pathname` property, causing it to be `undefined` at runtime despite `RequestServerOptions` declaring it as `pathname: string`. - Add `pathname: url.pathname` to server function middleware execution - Add `pathname: url.pathname` to page request middleware execution The route-level middleware in `handleServerRoutes` already passes `pathname` correctly. Closes TanStack/router#6647 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * test: add regression test for pathname in global request middleware (#6647) Add e2e tests to server-functions-global-middleware verifying that pathname is correctly passed to global request middleware in createStartHandler. - Add pathnameMiddleware that captures pathname from server callback - Add dedicated pathname-middleware route and test page - Verify pathname value on both SSR and client-side navigation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * refactor: remove unnecessary `as any` cast from pathname middleware test The middleware type system correctly infers `requestMiddlewarePathname` on the context, so the explicit cast is not needed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * ci: apply automated fixes --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
3 days ago
by kkznch
k
Canceled
6648
cf247bb8 refactor: remove unnecessary `as any` cast from pathname middleware test The middleware type system correctly infers `requestMiddlewarePathname` on the context, so the explicit cast is not needed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
4 days ago
by kkznch
k
Previous page
Previous
Next
Next page