We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A client-side request to Algolia is done, even though it was already server-side rendered
pnpm dev
http://localhost:3000
https://github.com/chrisvltn/instantsearch-extra-fetch-issue
No request to Algolia is done client-side when entering the page
[email protected] [email protected] [email protected]
MacOS
Firefox
The text was updated successfully, but these errors were encountered:
fix(client): ensure client.search is bound
57dfd44
fixes #6350 fixes algolia/algoliasearch-client-javascript#1549 possibly also solves #6348, to investigate afterwards
fix(client): ensure client.search is bound (#6352)
2a171a9
* 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
Sorry, something went wrong.
@Roypoe The issue is still happening. I updated the libraries in the reproducible repo and it still happens :(
Successfully merging a pull request may close this issue.
🐛 Current behavior
A client-side request to Algolia is done, even though it was already server-side rendered
🔍 Steps to reproduce
pnpm dev
and go to your localhosthttp://localhost:3000
Live 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
[email protected] [email protected] [email protected]
Operating system
MacOS
Browser
Firefox
Code of Conduct
The text was updated successfully, but these errors were encountered: