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
useSearch on a dynamic hook
Nested route different layout

Router context indeterministically using the initialValue instead of the passed value
beforeLoad the router context sometimes use the value I passed to it and sometimes it uses the defaultValue (undefined in my case). Isn't the context supposed to always use the value provided to it?How to hide back button?
router.back() but I want to hide this button if router.back() would go out of the app. (For example, if you open a new tab and then go to the URL of the app, router.back() will work until it will go back to the new tab)....Possibility of showing a spinner / loader prior to beforeLoad delay of 500ms
<LoadingView/> to the user while convex and clerk is done loading auth. this takes approx 700ms after that the beforeLoad happens and doens't return before 500ms which results in a white screen in that time span.
My question is... is such a delay for this beforeLoad normal? and if so, could i show my loading spinner again while beforeLoad returns?...How to add debounce to loader
Search Params -Date parsing
Router set up for a complex app
app.my-company.com and the external view is served at subdomain.my-company.com where subdomain is our customer's slug.
I want to serve different routes in the internal view and the external view. Currently I have the same repo deployed on all subdomains and in my CRA + react router setup, I serve either the internal routes (if it is a reserved subdomain) of the external routes (if there is a non-reserved subdomain). ...useSearch with validateSearch in _layout
Can I prevent path parameters (specifically @) from being escaped?
Router layouts inside subdirectory and prefixing

i18n Route Match
Access routes other than route leads to cannot get route
/raffle-details/$id, or reload that page, it'd work normally in dev server (vite).
The issue happens with the build. I ran live-server and it was able to open the root route, then the details route. But if I access the details route directly, or reload that page, I'll get Cannot get page (screenshot).
I try adding a notFoundComponent, it was not able to load this component as well....
Adding additional info to a route configuration
apply upper level layouts to nested routes
file-based routing and nested paths (seems to be broken)
Isolating Table Loading State Without Triggering Higher-Level Loaders
autoCodeSplitting causes entire app rerender
autoCodeSplitting on:...Cant enable autoCodeSplitting
How to skip reloading data