Nuxt 3 + Vue-InstantSearch SSR – global <AisInstantSearchSsr> wrapper with dynamic slot children fails to hydrate #6646
Unanswered
mustafadalga
asked this question in
Q&A
Replies: 1 comment 1 reply
-
|
Have you dug inside the internals of InstantSearch to find at which level the widgets aren't available? Normally there's code to propagate and evaluate the slots, but maybe there's a bug with nuxt 3? Happy to accept a PR if you find the cause and solution. |
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.
-
Goal
Have one global, SSR-enabled
<AisInstantSearchSsr>at the root of my Nuxt 3 app while each route brings its own set of InstantSearch widgets via slots.Minimal repo
Repo: https://stackblitz.com/edit/nuxt-starter-v7akze42 (fresh Nuxt 3, Vue-InstantSearch latest).
app.vuecomponents/InstantSearchProvider.vuepages/index.vuecomponents/Hits.vueExpected
On first load view-source should contain rendered hits (proving SSR) whichever route is visited.
Actual
Tried
All rely on widgets being rendered inside the provider component itself, not via slot.
Question
Is there an official pattern (or internal limitation) that prevents SSR when widgets are supplied through a slot?
If not, what’s the recommended way to keep one global, SSR-capable InstantSearch root while letting each page dynamically inject its own widgets ?
Beta Was this translation helpful? Give feedback.
All reactions