Correct way to not unmount a client component during soft navigation #79317
Unanswered
Luk-z
asked this question in
App Router
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Imagine a catchall route that fetch page structure based on pathname (aka ssr). The fetch and component render should be placed in page.tsx.
If two different pathname has same page composition (render same react components) is there a way to not unmount all (or some) page components during client navigation (sof navigation)?
I think this is not a pattern supported in next app route, but could be a common situation.
Beta Was this translation helpful? Give feedback.
All reactions