react-query-questions
solid-query-questions
table-questions
virtual-questions
router-questions
react-charts-questions
ranger-questions
vue-query-questions
svelte-query-questions
bling-questions
form-questions
angular-query-questions
start-questions
db-questions
start-showcase
router-showcase
📣-announcements
Before load not working in child routes

Is it possible to navigate to a file component that is OUTSIDE the route tree?
Why specify route path in code for file-based routes?
Tanstack Start with Clerk and Convex
/dashboard/transactions/incomes on first render (I was logged) I'm getting error shown on image.
Most important code parts:...
Redirect to throws type error on dynamic route
Keeping large object in search params causing too long URL.
Extracting Link props while retaining type safety
Authentication with tanstack-router
Advice on path-based i18n without lazy-loading or importing every language on the client.
Client side routing 404 error on refresh.
Validating Request Body, Typing API Routes, and Middleware Authentication in TanStack Start API
1. Validating Request Body
I’m currently validating the request body in a
POST route using Zod with safeParse, but request.body has to be validated like so:
...All child routes in a single bundle?
running beforeLoad auth in __root.tsx, but which needs access to a Context

Routing issues with better-auth
/auth/signin? (the '?' is actually tacked on) when better-auth's signin runs. I don't know what is doing the navigation nor why it appends a '?'.
2. TanStack's navigation doesn't work inside better-auth's signin onSuccess callback. I've tried router.navigate and useNavigation with and without router.invalidate() and router.invalidate({sync: true})
The call to better-auth's signin function looks like this:...Need advice on authentication
Conditionally loading route tree based on user type
virtual file route
How to retrieve "latest params" when loading a route?
Unexpected Loader Re-Requests on Current Route Hover with Preload ‘intent’
Change parent layout based on child route matching
useLoaderData({ from: "child route" }) but it throws if the child route is not matched.
Is it recommended to un-nest from the parent routes and just render the layout in the child route? If I do that, I can't grab the parent loaded data which means I have to repeat the parent data loading in the child route, it's not a problem, but I just wanted to know if there's a better way. Cheers...