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
custom metadata field on createFileRoute
head property, i can add certain metadata and introspect it at build time by reading the generated routeTree object, but this will end up inserting it into my html. Is there a better place to define build time metadata associated with a route?
Or a way to extend my router to enable this in a type safe way? I've attached 2 screenshots of how i'm reading / writing to the head property currently...
How to know when viewTransition is finished?
Type safe create url
Why use `beforeLoad()` to handle breadcrumbs? Shouldn't we use `context()` instead?
context() => any function available which seems to be made for that. why even the docs don't use it? is it for another purpose?Export variable is not defined in "ssr.mjs"
Reference of `navigate` now changes before navigation. Is this intended?
1.131.28 (latest as of now) if you have this kind of code:
```ts
function RouteComponent() {
const navigate = Route.useNavigate()...prefetchQuery vs ensureQueryData in SSR
What is the correct way to set up these routes with a layout ?
vadashboard and that route also has a _layout hierarchy goes as:
```
routes/
├── vadashboard.tsx (Main route - client selector page)
├── vadashboard/...Layouts in FileRoutes

Storing a list of urls to be navigated through later
navigate through. Worst case scenario I just serialize entire LinkProps objects and disable type checking for the line but I imagine there's a better way. I checked all the functions being exported and none of them seemed like they fit the bill, but it must exist where the lib parses the window href into matchable json
For context this is a react SPA with no ssr...Multilingual URLs
/en/about and /fr/a-propos). How easy/difficult would something like this be to implement in TanStack Router?
Obviously, the ideal implementation would be a single .tsx file per route, where /en/about and /fr/a-propos both point to (for example) about.tsx.
We've successfully implemented this in RRv7, along with a supporting <Link> component that will render the correct URL path depending on the current locale.. but I'd like to explore TanStack Router for new projects....SingleSPA MFE React Router issue (advise for migration to TanStack Router)
Custom Template for File Based Routing?
Catch all route for showing a modal over existing pages
Error while using useNavigate hook with react router

Dev workflow for building a pendingComponent?
pendingComponent? I change pendingComponent to component whilst im developing / designing the loading state, then change it back to pendingComponent when I'm happy. I'm wondering if im missing something obvious?errorComponent not rendering
notFoundComponent and errorComponent defined for a layout with some child routes defined in route.tsx. The notFoundComponent is getting rendered correctly when a route is not found but when an error occurs within those child routes, instead of rendering errorComponent, it's rendering defaultErrorComponent defined in router.tsx which is not the behavior I am expecting. Is this the correct behavior or I am missing something?...How to handle notFound errors based on route param validation?
/posts/$postId where I essentially just call a server function to get the relevant post:
```ts
// route
export const Route = createFileRoute("/posts/$postId")({...React RSC in Router