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
Blocker and link
File System Routing: Multiple levels of nesting in a single directory
When deploying on vercel, getting 404 when visiting a lazy loaded page after hard reload+cache clear
createLazyFileRoute and index.lazy.tsx strategy. When visiting a page that's lazy loaded (for eg. /dashboard) I get 404 not found and then I have to visit / (the only route that's not lazy loaded) and then visit other routes.
This only happens when deploying on vercel, when building locally, it works fine....Lazy Loading Rec'd Approach?
routes/expensive/index.tsx looks like this:
```ts...Router context and beforeLoad race condition
NotFound never reached
Page not reloading

<Link>, useNavigate makes that variable routes are not updated -> they need a reload
product/1 for example, makes that sometime, it will render the product/2 because it was in cache, then if I reload the page, the good content is show. Can I do something about it ?Protect all routes with a redirect
index.tsx vs index.route.tsx
For example, if you have a route file named posts.tsx, you would create a new directory named posts and move the posts.tsx file into that directory, renaming it to index.route.tsx....
Is this possible to update the context programmatically without using beforeLoad
nested routeFilePrefix

Nested path being caught by parent route

Type assignment flip in LoaderFnContext
RouteCollector<TRoute extends MyAppAnyRoute = MyAppAnyRoute> it works well until reaches that type in shouldReload.
At this moment, it tries to reverse-validate that my MyAppAnyRoute satisfies the exact route that I'm declared. It's like intentionally at some point tries to assign AnyMatch to the declared ExactMatch. Any ideas why it may happen?...
Global search param
Am I doing something wrong with the loader function?

Can't modify router context from within a component
Is there a way to not inherit the search parameters from the parent route?
How to get the search param using useSearch() at the first time?
Non-Nested Routes with matches and breadcrumbs
