-
Notifications
You must be signed in to change notification settings - Fork 172
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
Compatibility with Angular Universal #66
Comments
No, I'm afraid the slider component is currently very closely tied to the browser. To support something like Angular Universal, the slider layout would need to be re-written to use pure CSS in some clever way. I would have to research this further to see if this is possible. It would be actually a good thing to do, because it would also solve current performance issues. |
see #74 , to avoid wrap ng5-slider element with *ngIf, if it wouldn't render in the ssr it won't run the error in server side. |
just put in the constructor like this:
and
in the element that wraps ng5-slider component |
I have replied to the PR in #74 - this is a quick workaround, which does not solve the underlying problem. I have declined the PR as a result. I have documented no support for Angular Universal as a known issue for now. I will keep this ticket open until a long-term solution is found. |
+1 for a more elegant solution to this problem |
@harellevy thank you very much for this. It has resolved the |
same problem for showing modal in angular universal. |
const domino = require('domino'); #66 Angular SSR only |
@harellevy Thank you very much. I had same issue while using angular-responsive-carousel with SSR. It resolved my issue. |
Thank You Very Much! |
Hello,
I'm trying to integrate the component into my app, using Universal server-side rendering.
My code works fine (thanks for this good component!) without the SSR.
When running with SSR, this error occurs :
So it seems that the component doesn't deal with SSR constraints (no access to browser window, etc..).
Should it be possible to make this component working with Universal ? In the meantime, did someone find a workaround ?
The text was updated successfully, but these errors were encountered: