Server rendering causing two renders on each side (twice on server, twice on client) about apollo-link-state

[jbaxleyiii]

➤ James Baxley commented:

@lostpebble hmm that is no good! Do you have a simple reproduction I can take a look at?

[jbaxleyiii]

➤ Paul Myburgh commented:

@jbaxleyiii sure, I took my current project and tried to strip it down as much as possible to create something you can run and check out:

https://github.com/lostpebble/apollo-two-render

Hope it's not too verbose. The main files to look at are ServerRenderReact.tsx and entryProd.tsx

• for the server side rendering. And then entryHot.tsx for the client side rendering.

[jbaxleyiii]

➤ Jihoon Kim commented:

@jbaxleyiii any update on this?

[jbaxleyiii]

➤ stale[bot] commented:

This issue has been automatically labled because it has not had recent activity. If you have not received a response from anyone, please mention the repository maintainer (most likely @jbaxleyiii). It will be closed if no further activity occurs. Thank you for your contributions to React Apollo!

[jbaxleyiii]

➤ xabree commented:

I have same issue when using getDataFromTree on server side :(, any Update on this ?

[jbaxleyiii]

➤ stale[bot] commented:

This issue has been automatically labled because it has not had recent activity. If you have not received a response from anyone, please mention the repository maintainer (most likely @jbaxleyiii). It will be closed if no further activity occurs. Thank you for your contributions to React Apollo!

[jbaxleyiii]

➤ Maxim Vorontsov commented:

Any updates on this issue?

[jbaxleyiii]

➤ stale[bot] commented:

This issue has been automatically labled because it has not had recent activity. If you have not received a response from anyone, please mention the repository maintainer (most likely @jbaxleyiii). It will be closed if no further activity occurs. Thank you for your contributions to React Apollo!

[jbaxleyiii]

➤ Marc Alexandre commented:

I can't say for the server rendering code, I've yet to use something like this. But for the client side, it seems logical to have two render. Maybe it's different in typescript from pure javascript, but a graphql query would first send { loading: true, allLinks: undefined } and then send { loading: false, allLinks: ...YOUR_DATA }, which would make 2 renders with your code. And if the "loading" is managed differently in typescript, there is also #1314 that can maybe cause this?

[lostpebble]

@jbaxleyiii I'll be able to confirm if this is still an issue for you again soon. Is there a reason you're closing it besides it being a bit stagnant?