Where would you rehydrate the store?

@pjmagee Could you use https://github.com/btroncone/ngrx-store-localstorage to rehydrate from localStorage. Should work with angular 4.x as well.

@hakonamatata @MarkPieszak would it be interesting to see an example of an XHR request to an REST API, which in turn updates the client store via something like https://github.com/ngrx/effects?

@estebanvega @MarkPieszak but what about SSR since ngrx-store-localstorage has browser dependencies? Also what about authentication? When a user is authenticated and the site is refreshed, then authentication is lost from the store...and....do you really want to store that information in local storage? :)

Actually,, SSR seems so pointless right now, many third party components will just break if you have SSR enabled. Things like PrimeNG etc.

A lot of those decisions (on what to pass down from server->client) and such you'd need to decide for your project what's important to do that with, and what you can live without rendering on the server (and let it just happen on the client).

PrimeNG unfortunately entangled their library into the DOM instead of using Renderer and other abstractions provided :/

On the bright side though! We are working on adding a mocking layer over the window/document/etc so that it will be more flexible and hopefully better accommodate libraries that are accidentally (or not) using the DOM, so that they will still be able to Render in a server-render. 👍