This repository has been archived by the owner on Dec 30, 2022. It is now read-only.
Powered-by component is not SSR compatible #367
Comments
|
Oh thanks for noticing that. Feel free to add a pr if you want |
|
I'll try to leave a PR tonight! for now I've wrapped it in a nuxt |
Jexordexan
pushed a commit
to Jexordexan/vue-instantsearch
that referenced
this issue
Dec 4, 2017
Add a null check to the `location` reference in `algoliaUrl`. fixes algolia#367
rayrutjes
added a commit
that referenced
this issue
Dec 4, 2017
fix: Powered-by component is not SSR compatible #367
|
Hey @Jexordexan , this is now release in v1.3.3 Let me know if it works out properly now. Thanks for your work! |
|
Please reopen. Error: |
|
Hmm @ishitatsuyuki, are you using the latest version? The PR has been merged to fix this almost a year ago. Can you give a GitHub project where you receive this error? |
Haroenv
pushed a commit
to algolia/instantsearch
that referenced
this issue
Dec 28, 2022
…arch#367 Add a null check to the `location` reference in `algoliaUrl`. fixes algolia/vue-instantsearch#367
Haroenv
pushed a commit
to algolia/instantsearch
that referenced
this issue
Dec 28, 2022
fix: Powered-by component is not SSR compatible algolia/vue-instantsearch#367
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Do you want to request a feature or report a bug?
bug
Steps:
Create an empty
nuxtstarter project and installvue-instantsearchadd an
<ais-powered-by>component into one of the templatesrun
npm run devvisit the page with the component and notice the error screen saying
location is undefinedBug: What is the current behavior?
<ais-powered-by>is not SSR compatible,Bug: What is the expected behavior?
The component should be compatible with ssr
Bug: What browsers are impacted? Which versions?
This is an SSR issue, so node.js?
Bug: What is the proposed solution?
Add a null check for the
locationobjectWhat is the version you are using? Always use the latest one before opening a bug issue.
1.3.2
The text was updated successfully, but these errors were encountered: