Instantsearch server-side rendering is also fetching on the client when using multi-index query in development environment #6348
Labels
triage
Issues to be categorized by the team
Comments
Haroenv
added a commit
that referenced
this issue
Sep 9, 2024
fixes #6350 fixes algolia/algoliasearch-client-javascript#1549 possibly also solves #6348, to investigate afterwards
Haroenv
added a commit
that referenced
this issue
Sep 10, 2024
* fix(client): ensure client.search is bound fixes #6350 fixes algolia/algoliasearch-client-javascript#1549 possibly also solves #6348, to investigate afterwards * fix lint
|
Hi @chrisvltn die you know if that issue was fixed by that commit below? Thx |
|
@Roypoe The issue is still happening. I updated the libraries in the reproducible repo and it still happens :( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 Current behavior
A client-side request to Algolia is done, even though it was already server-side rendered
🔍 Steps to reproduce
pnpm devand go to your localhosthttp://localhost:3000Live reproduction
https://github.com/chrisvltn/instantsearch-extra-fetch-issue
💭 Expected behavior
No request to Algolia is done client-side when entering the page
Package version
instantsearch.js@4.74.0 algoliasearch@5.2.5 react-instantsearch@7.13.0
Operating system
MacOS
Browser
Firefox
Code of Conduct
The text was updated successfully, but these errors were encountered: