-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
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
need SSR usage example #17
Comments
Thanks for this, I'll take a look at updating the docs to include handling SSR when I get the chance. |
FYI for people using Nuxt and are ok with only rendering this component client-side, there is the
nuxt/nuxt#1558 template on client side |
@craigh411 thanks a lot for this component! |
@xloading Yes, that's definitely worthwhile! I've opened a separate issue for this request. |
|
Any update on this? no-ssr is not working for me, getting the error from the point when I add StarRating to the components. |
I have seen this issue in version |
Thanks you, But I think this package should be update at this point |
Following this link (https://stackoverflow.com/questions/60735985/cant-add-npm-package-to-nuxt-js-vue-star-rating) and then wrapping component with client-only seems to work for nuxt. |
For nuxt, this worked for me:
|
@bunday Doesn't work in nuxt 3 rc update nuxt 3 solution :
Then directly use |
Using this solution, the component seems to work in Nuxt 3, but the console show some warns.
|
Is there a solution for Vite/InertiaJS? |
I suffered with this task for 5 hours, this solution helped me. Instead of standard import, use a const.
It's strange why the developers don't add this information to the documentation? |
I'm rendering my pages on server side and I found a problem that only occurs on first page render.
When I'm trying to access a page with StarRating I get the following error:
Call stack gives much more info
Due to vue-style-loader page you need to build server side files with
target: 'node'
to prevent this from happening.After a short research I solved this problem by changing import to
Maybe it's worth adding in
README.md
to prevent inexperienced users like me from this errorThe text was updated successfully, but these errors were encountered: