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
{{ message }}
This repository has been archived by the owner on Mar 20, 2024. It is now read-only.
Which parts of preboot are affected by this issue?
server side
client side
inline
build process
docs
tests
Do you want to request a feature or report a bug?
Report a bug
What is the current behavior?
When loading a page with preboot installed, http calls are being run twice, once by the server and then again when the client app takes over.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem by creating a github repo.
Load a page which makes a http call (in this case using a resolve using the router)
The page is correctly loaded but when checking logs, you will notice that the http call has been made twice
What is the expected behavior?
The data to be cached instead of the request being called twice
Please tell us about your environment:
Browser: [Chrome 58.0.3029.110 (64-bit)]
Language: [TypeScript 2.3.4]
OS: [Mac OS X]
Platform: [NodeJs 6.9.4]
The text was updated successfully, but these errors were encountered:
Yes, as @marekstabla mentions, you need to cache data between the server and client which requires the transfer state module. Preboot is just focused on the events between the server view and client view (i.e. if someone clicks on something in the server view before the client view finishes bootstrapping).
Note: for support questions, please use the Universal Slack Channcel or https://gitter.im/angular/universal
Do you want to request a feature or report a bug?
Report a bug
What is the current behavior?
When loading a page with preboot installed, http calls are being run twice, once by the server and then again when the client app takes over.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem by creating a github repo.
What is the expected behavior?
The data to be cached instead of the request being called twice
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: