#You’re not supposed to use react router

1 messages · Page 1 of 1 (latest)

modest charm
#

Hi Joulev, I'm just following the SPA suggestions on NextJS docs. I'm not using next router at all right now

hallow pineBOT
#

Hi @modest charm. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

Sorry @modest charm, I seem to be having a bit of trouble. Don't worry though, I've pinged my supprt and they will try to fix me up! :technologist:

Perhaps try again in 15mins?

wise canopy
#

Can you give me the link?

#

I have never seen tanstack router working fine with nextjs router before

modest charm
#

We're not using the NextJS router at all right now, we're using it as a SPA basically.

wise canopy
#

Then it doesn’t work. Nextjs has a built in router that is deeply integrated to the framework, you cannot bring your own router in

#

If you want to use tanstack router, use a framework that supports it or uses it under the hood

modest charm
#

They say (used to say) this is an OK pattern, we just have a single global route [[app]] and then use react router from there. It's working fine for us

wise canopy
#

From the issue posted in general, it is not working fine though is it?

#

They dont play together well

#

So even when you somehow miraculously made it work, migrate to the nextjs router as soon as possible