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
OAuth login flow with TanStack router
Do layouts work in router folder groups?

Pathless layout with standard layout
/auth/register
/auth/login
/auth/register
/auth/login
Navigate should use input type params not output type params.
navigate still require search params even if they are marked as optional and resolved with default or catch. Unless I'm missing something. Stackblitz with example: https://stackblitz.com/edit/tanstack-router-vkzaga?file=src%2Froutes%2Fposts.tsx
```typescript
import * as React from 'react';
import { createFileRoute, Link, Outlet } from '@tanstack/react-router';...Best practice for route alias?
/playlists/$playlistId
/library/$playlistId
Is there any best practice to have minimal boilerplate to make this happen? Right now I've defined a PlaylistView component in routes/-shared/PlaylistView.tsx which also exports a re-usable "route config" object for the loader. ...Possible to escape parent nesting inside a folder?
Lazy file route use cases
beforeload with async does not seem to wait or creates infinite rerenders
Transforming backend filters in the loader to frontend params.
Any plugins for rspack or webpack support?
redirect in beforeLoad/loader causes infinite loop
_authed,
```
export const Route = createFileRoute("/_authed")({
component: LayoutComponent,
beforeLoad: async ({ context: { queryClient } }) => {...[FIXED] Prevent Router's loader to rerun when the hash changes
Easiest way to make the possible routes/paths accessible when browsing it directly
Automatically generate file routes on save
Navigate to an external url prob
loaderDeps / loader function race condition.
Sync router with other router (ex vue router) for a micro-frontend setup
Dynamic breadcrumbs
/projects/123) which can be navigated to from 2 different routes (/projects and /customers/456). Depending on the route I have come from, the breadcrumbs in the project route should show the correct previous route.
Is there a standard for how to implement this? If I store it in a context, then what happens when someone refreshes the page? If I use localstaorage instead, there could be multiple tabs to track which can make it a bit more complicated.
I just want to make sure I am doing everything right from the start with tanstack router. I need this for the project route today but what if I need it for some other route in the future? How should I be configuring things?...Does it make sense to start with Tanstack Router for electron.js app
Weird errors (only in production) with following structure