Great video, thank you for the clear explanation and demonstration of the features, specifically the loader part where you also included tanstack query as the external data library.
I think there is a redundancy with your QueryClient - since you are wrapping everything at the top level, I don't think you also need to configure a context. Maybe I am wrong?
The advantage I could think of is you could pull in the queryClient in other files and do stuff with it. The docs do suggest to use the queryClient. Not really sure if entire thing would work without one though. I’d def not remove it tbh. But yes, interesting and would love to dig deeper about this
@@AtharvaDeosthale I could be wrong, but is this where useQueryClient comes in handy? It will simply return the current queryClient instead of instantiate a new one for each route.
Great work! I just realize that instead of using `_layout.tsx`, we can use `_layout/route.tsx` as well. I prefer that because it feels much cleaner. 👾 Thank you!
Straightforward, informative, and clear. This is very helpful. Thank you!
Great video, thank you for the clear explanation and demonstration of the features, specifically the loader part where you also included tanstack query as the external data library.
i searched a lot the way of layout finally i got it 💕
nice bro we want more on this tanstack router from beginer to advanced very nice keep it up
Sure 👍
@@AtharvaDeosthale when you will upload new vidio on tanstack router
Really good tutorial, keep it up!
Very useful, thank you!
Good video. thank you 💐
Thank you so much !!
Very usefull fir me thanks
Thanks, bro you helped me a lot. I was stuck at file configuration. I have a question does React Route work without React typescript?
TanStack router SHOULD work with JavaScript I think. I have only tried with TypeScript. But yeah if you use JS, you wont get the type-safety features.
@@AtharvaDeosthale Got it, Thank you
why use this instead of NextJS routing behavior(page router)?
Some people simply don't prefer Next.js for their own reasons. TanStack router can help you bring file based routing to Vite
It gives very robust state management in url, which is how nextjs prefers it but does not have that in the router itself
I think there is a redundancy with your QueryClient - since you are wrapping everything at the top level, I don't think you also need to configure a context. Maybe I am wrong?
Nvm, I see that the context is needed specifically for the router, not for TS Query
The advantage I could think of is you could pull in the queryClient in other files and do stuff with it. The docs do suggest to use the queryClient. Not really sure if entire thing would work without one though. I’d def not remove it tbh. But yes, interesting and would love to dig deeper about this
@@AtharvaDeosthale I could be wrong, but is this where useQueryClient comes in handy? It will simply return the current queryClient instead of instantiate a new one for each route.
The problem there would be that hooks cannot be used on server components
@@AtharvaDeosthale You are absolutely right, and the way you did it is NOT creating a new instance of the query client each time. I was too fast ;)
Bring a brand vedio on trpc, monorepo, turborepo 😅
I have individual videos on them. Do you want me to create a project using all of them together?
👍yes
Good video but lacks Authentication Routes tutorial
Would love to cover it in some tutorial
Great work!
I just realize that instead of using `_layout.tsx`, we can use `_layout/route.tsx` as well. I prefer that because it feels much cleaner. 👾
Thank you!