why theo uses react router on his nextjs projects ?
so what's the point of using react router in nextjs instead of app router ? and is that change how nextjs render the site ?
Solution:Jump to solution
to get the best of both worlds? I can't comment on how someone else thinks, but seeing the code of t3.chat in the latest video, i see that he used nextjs possibly to make keep everything fast in the UI side and render components SSR way but wanted to use client side routing to keep it simple for having param based routing?
in next js if you are going to use hooks, then that page or component will need to be declared with 'use client' at the top of the file. In t3 chat's case, i see that the chat pages are mostly using hooks, so again keeping them in nextjs app routing or not, doesnt' make much diff.
However, let me tell you, i have also made a ai chat web application in nextjs with clerk auth (theo mentioned that he wanted to but didn't take the time to for t3 chat). The problems i faced when using 'use client' and then again having to scope out the components, etc, etc, better i should have just used react routing instead from the beginning as well. But glad i stuck with nextjs, cause there's really not a lot of pages with an AI chat application, and it needs to be fast too....
1 Reply
Solution
to get the best of both worlds? I can't comment on how someone else thinks, but seeing the code of t3.chat in the latest video, i see that he used nextjs possibly to make keep everything fast in the UI side and render components SSR way but wanted to use client side routing to keep it simple for having param based routing?
in next js if you are going to use hooks, then that page or component will need to be declared with 'use client' at the top of the file. In t3 chat's case, i see that the chat pages are mostly using hooks, so again keeping them in nextjs app routing or not, doesnt' make much diff.
However, let me tell you, i have also made a ai chat web application in nextjs with clerk auth (theo mentioned that he wanted to but didn't take the time to for t3 chat). The problems i faced when using 'use client' and then again having to scope out the components, etc, etc, better i should have just used react routing instead from the beginning as well. But glad i stuck with nextjs, cause there's really not a lot of pages with an AI chat application, and it needs to be fast too.