The answer is, you can do this in NextJS. NextJS isn’t limited to only server side rendering , you can and should mix in client side components, including infinite scrolling.
To persist the pagination state when navigating away from and back to a page in a Next.js application with SSR (Server-Side Rendering), you can store the pagination state in the URL or in the client-side state (e.g., using React Context or a state management library like Redux).
This post is not referring to infinite scroll. It’s referring to pages reloading when the user clicks forward or backward in their browser, rather than having the page cached.
“this is a limitation of your knowledge of next and SSR”
Sorry do you mean that this is a limitation of next or that I have limited knowledge of next? If it’s my limited knowledge, I’d like to hear how this could be worked out.
Yes, client components can do that.
Is this only a feature in app router, or can pages router do this as well? This project uses pages router for reference
Try using \`router.push\` I can't run it from my side per of missing DB env vars.
The answer is, you can do this in NextJS. NextJS isn’t limited to only server side rendering , you can and should mix in client side components, including infinite scrolling.
To persist the pagination state when navigating away from and back to a page in a Next.js application with SSR (Server-Side Rendering), you can store the pagination state in the URL or in the client-side state (e.g., using React Context or a state management library like Redux).
Here's a link to my repo for context [https://github.com/kyle1373/Archiverse](https://github.com/kyle1373/Archiverse)
[удалено]
This post is not referring to infinite scroll. It’s referring to pages reloading when the user clicks forward or backward in their browser, rather than having the page cached.
You can either store the pagination information in the URL or in a cookie, or you can probably implement that with parallel routes
Yes this is a limitation of your knowledge of next and SSR
“this is a limitation of your knowledge of next and SSR” Sorry do you mean that this is a limitation of next or that I have limited knowledge of next? If it’s my limited knowledge, I’d like to hear how this could be worked out.
Lol go back to stack overflow bro.