Skip getServerSideProps on client routing

[isBatak]

Is it possible to skip getServerSideProps when navigating from one page to another on the client?
I want to prerender a page (SSR) when the user lands directly to the URL but when he navigates via client navigation I want to use useSWR and show the page with some skeleton loaders.
Is that currently possible?

[aralroca]

I have exactly the same behavior under getInitialProps and I'm also looking for a solution before migrate from getInitialProps to getServerSideProps.

Anybody knows if there is any way or any plan to support that?

A suggestion: add some option to the return:

async function getServerSideProps() {
  return {
    props: fetchProps(),
    navigation: false,
  }
}

[isBatak]

Yes, I was thinking about the same thing, some boolean value returned from getServerSideProps :D

[markbrocato]

We'd like to see this as well. If we went ahead and sent a PR to implement this spec ^^, would it be accepted? Is this already in progress. Happy to help if no one else is working on it.

[timneutkens]

Open feature request here: #11897
You can't open a PR with that approach because it wouldn't work (as outlined in my replies on that feature request).

[kamilml]

I have exactly the same problem. I want to skip getServerSideProps in the client. Any solution or new idea? I'm getting crazy with this :(

I already spent 1 whole day trying to read my redux store (because I can save a value to prevent a useless query inside getServerSideProps) but I can't.

[thiagoloddi]

Is it just me or running getServerSideProps every time you change pages kind of defeats the purpose of a SPA? I want to make use of apollo-client in-memory cache but it's not possible, because whenever I change pages all the data is fetched again from the network in the server-side.

Is there a reason why it's implemented this way? I thought the option shallow should apply for changing routes within the app, not only when in the same page.

[leerob]

#29117 (comment)