You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It wasn't something that was explicitly planned. That said, it seems like the only issue is that window.setTimeout calls are being executed server-side and wrapping with a check would enable SSR?
My understanding is that yes: protecting just those calls would enable SSR. I'd do it myself but don't know the first thing about developing/testing a node module.
This isn't something I've spent much time testing either, although the change is trivial. I have a set of changes I'm putting together for release this week. I'll add this and I can make future adjustments based on implementation feedback.
Hello,
Are there any plans to support Angular Universal SSR? That is, checking
isPlatformBrowser()
before attempting to reference thewindow
object? Thanks!The text was updated successfully, but these errors were encountered: