How can/should this be used with nextjs? #346
-
|
Hi! I've idly browsed through the docs for react-location and thought this sounds great, but we wouldn't consider abandoning nextjs completely, given the many benefits we get from it (and the many we expect from next 13 and beyond). Is there a recommended way to use react-location in nextjs projects, or even a hint of how to start thinking about things? Or are they fundamentally incompatible? Would be really interesting to see a nextjs project in the examples folder. I saw #44 and it was resolved with a link to a comparison page, but that only seems to compare with react-router. I also found #95 which asks "can this be used with nextjs" and the answer was "yes". Which is great, but would be great to know more about how, or if there are any pitfalls to look out for. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
Right now, TanStack Router is not designed to be used with full-stack frameworks and is best suited for client-side only apps. In the future, we will be addressing SSR and framework integration. With regards to those issues, you can use client-side routers inside of Next and other full-stack frameworks, but you are essentially opting out of the SSR patterns and benefits you get from their routers. |
Beta Was this translation helpful? Give feedback.
-
|
is this still true with the latest release? |
Beta Was this translation helpful? Give feedback.
-
|
Would like to know too |
Beta Was this translation helpful? Give feedback.
-
|
@tannerlinsley still true? |
Beta Was this translation helpful? Give feedback.
-
|
take a look at this in the mean time 😀 probably it can help you |
Beta Was this translation helpful? Give feedback.
-
|
Would love to hear an update on this - i.e. the recommended policy for Migrating from Next.JS, or maybe wait until Start is out, or is it not an option? Have a few-pages Next.js app (pages router) that I'd love to convert. |
Beta Was this translation helpful? Give feedback.
Right now, TanStack Router is not designed to be used with full-stack frameworks and is best suited for client-side only apps. In the future, we will be addressing SSR and framework integration. With regards to those issues, you can use client-side routers inside of Next and other full-stack frameworks, but you are essentially opting out of the SSR patterns and benefits you get from their routers.