@@orcdevno, I don't. But I was wondering if you had because I'm not sure if it is needed. Remix hooks provide many of the functionalities of tanstack query and I wanted to know your take on it
what is different between normal fetch and this one fetch get calls how can cache, when i navigating between pages and come again same page its triggering api calls in devtools networks, actually we don't want trigger again and again api calls right? by default its not provide cache tanstack query?
Great question! Now with Next.js 15 there is no basically much difference, except with TanStack we are getting all the properties like `isPending`, `isCompleted` etc Lately I'm not using TanStack on newer projects, because there really isn't much difference anymore.
@@cant_sleeeep Yeah just checked it out, it's type safe, and it gives autocompletion of tables, columns etc I'll definitely try it out! Thanks on this one! ⚔
from their docs: Kysely IS NOT an ORM. Kysely DOES NOT have the concept of relations. Kysely IS a query builder. Kysely DOES build the SQL you tell it to, nothing more, nothing less.
Believe me, I have never enjoyed a simplified explanation like this before. You are amazing. Keep it up, man. I wish you success
Thank you so much for your kind words bro! I'm really glad to hear that. Your support means a lot! ⚔️
2:16 Thank you!!
I was having errors following the official docs, this helped me fix it
Awesome to hear that! You're welcome! ⚔
Thank you so much!! Covered all the points I needed to get going quickly.
@@michaelndad You’re welcome! I am glad it was helpful!
i love your videos please bring more nextjs content and projects
I'm glad to hear you love the videos! I'll definitely create more Next.js content and projects for you. Stay tuned! ⚔️
Great video! Have you tried remix with tanstack query?
Thank you! No, haven't tried it yet. Any tips you have? :D
@@orcdevno, I don't. But I was wondering if you had because I'm not sure if it is needed. Remix hooks provide many of the functionalities of tanstack query and I wanted to know your take on it
what is different between
normal fetch and this one
fetch get calls how can cache, when i navigating between pages and come again same page its triggering api calls in devtools networks, actually we don't want trigger again and again api calls right?
by default its not provide cache tanstack query?
Great question!
Now with Next.js 15 there is no basically much difference, except with TanStack we are getting all the properties like `isPending`, `isCompleted` etc
Lately I'm not using TanStack on newer projects, because there really isn't much difference anymore.
how?, api route ? or any otherway?
@@dabbarnaresh7791 Server actions, api routes are not the way of doing things in Next.js anymore, except for some special cases.
Please make a video it's helpful
🥰🥰☺😊
@@dabbarnaresh7791 Will do!
Why didn't you rename the "todos" queryKey?
Good point! Should've renamed it to make it more clear :D
@@orcdev No worries. Thanks for your response here.
@@ImaginativeWork You're welcome!
Super
Awesome! Glad you liked it!
please use kysely instead of drizzle.
Never tried Kyseli :D
What is the difference? Why is it better than Drizzle or Prisma?
@@orcdev as far as i understand it allows querying directly but in a simpler way than drizzle, so without all the hassle
@@cant_sleeeep Yeah just checked it out, it's type safe, and it gives autocompletion of tables, columns etc I'll definitely try it out! Thanks on this one! ⚔
from their docs:
Kysely IS NOT an ORM. Kysely DOES NOT have the concept of relations. Kysely IS a query builder. Kysely DOES build the SQL you tell it to, nothing more, nothing less.
@@theBarracuda_ boo hoo