Replies: 1 comment 1 reply
-
|
This should work out of the box. Have you tried it out? |
Beta Was this translation helpful? Give feedback.
1 reply
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.
-
Cache components and a partial prerendering solution has finally landed in nextjs land. This gives, to me, an optimal solution how I think a search experience should work. When a customer lands on search page or listing page I want to render the initial result on the server, streamed in behind suspense, and then when it is on the client I want the client behavior to just work.
Will that work out of the box with InstantSearchNext or is there something that is needed? Or is it better to use the InstantSearchSSRProvider? The experience I am after is to have the initial result rendered on the server, not the response streamed in as json and then rendered on the client.
Beta Was this translation helpful? Give feedback.
All reactions