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
.env files in TanStack Start?
.env.staging
file and build with vite build --mode staging
) but wasn't sure if this was the right way to do things with TanStack Start or if there's a better pattern? I realize you can manually define env vars with your hosting provider, but it's nice to use .env
files for non-secret values (e.g. API base urls, etc)
Started discussion here: https://github.com/TanStack/router/discussions/3126...Two base-paths with each their own layout and outlets
Handling Both Dynamic and Index Route in one file
Should search parameter changes trigger route loader reloads when not specified in loaderDeps?
Tanstack router + React: Nx monorepo with module federation using Rspack
Im using tanstack router right?

is it possible to use tanstack start with code based routing?
Is it normal that the search params are stripped when they don't pass the validation?
useActive for nested children

useMatchRoute but don't re-render on every state change
How to create a child route of an index route?
/
) and have a child route at /verify
that renders a modal. Is there a way to achieve that using file-based routing?Loosing type safety when wrapping <Link>
<Link to="/invalid">
and I don't like that I loose the type safety.
```tsx
import { Link } from "@tanstack/react-router";
import clsx from "clsx";...Different routes based auth status
Is there a way to get proper search params in navigate without a specific route
/dashboard
route has a modal engine that's basically just a discriminated union of different modal types. Using that I am rendering different types of modals
```ts
// def...Handle notFound in a component
notFound
component in a route component (not the loader)? I won't know specifically if the page is a 404 until the query finishes, as I am in an $id
route and querying for that specific item. I'd like to throw notFound
if the query returns null....Index route not loading by default
__root.tsx
file and an index.tsx
(basically following the tutorial)
This works fine in dev mode, but when I do a production build, the app loads with a not found. In the tanstack dev tools, The matcher is only matching on __root__
so the <Outlet />
is rendering Not Found
.
When I click on the "Home" link, it routes to the correct place and everything is fine.
...
Invariant Failed: _authed to _non-authed Route
Why does `useLocation` re-render before navigation?
Has <Link to="." ... /> changed recently? I used to be able to update search this way.
useRouterState
and dump its respective state's pathname in. Here's an example of the workaround — <MenuItem />
is a lightweight wrapper around <Link/>
.The following used to work with
to="."
```...I18next Suspense mode with TSR