Replies: 4 comments 2 replies
-
|
this is the example of Relay team with nextjs |
Beta Was this translation helpful? Give feedback.
-
|
As |
Beta Was this translation helpful? Give feedback.
-
|
Also, the Relay team's example is awesome! Unfortunately it installs a global |
Beta Was this translation helpful? Give feedback.
-
|
@rrdelaney Just wanted to chime in and say that the relay team updated their example to use Curious if you think this is substantially different that your current approach? Thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Interesting. Thanks for the explanation! |
Beta Was this translation helpful? Give feedback.
-
Hey there! Just wanted to say thanks for this library which has been working wonderfully for my projects.
Now that React 18 has been released, I've been playing around with the nextjs experimental runtimes and have been trying to understand how to modify or implement a hydration strategy that allows use of the runtime.
Right now, if you enable the
nodejsexperimental runtime, the client errs with a message saying that the preloaded query is null. Checking the server logs, it looks like the preloaded query is returned on the server when it's rendered for the stream, but not when the client tries to hydrate it withusePreloadedQuery.What I can't unpack is whether this is a result of trying to hydrate the client twice -- once from
getServerSidePropsand then once again from the edge stream. I recall there being an issue a few months back, but would love to chat about it and/or help out implementing a streaming strategy for React 18.Thanks again!
Beta Was this translation helpful? Give feedback.
All reactions