same here :\

+1, the same here too....

After looking at the main cause of this problem I notice that it is related to the Angular/preboot.
as a temp fix for this I commented out this line :
setImmediate(() => prebootClient().complete());
inside the root.module.ts file
and the problem was gone.

Unfortunately I cannot reproduce this. Can you tell me what the initial HTTP request gives back in its body? Anyone - @ElderJames @wnabil @abdalrhman-alhomsi

I tested the example app and also has the same behavior, I think there is something wrong with preboot.

I have removed the setImmediate call in the example as it was unnecessary. Does this fix your issue? Maybe you are using an old Chrome that doesn't have setImmediate?

My chrome is at latest version and this issue happened also on firefox for me not only chrome.
Yes removing setImmediate works but also need to remove builder.preboot(true); in server/index.ts.