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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server doesn't seem to start until something in site-src is touched #4
Comments
Same issue here. |
Discovered that this is a feature. |
Hey; Thanks for posting. Actually, for me the server/browser-tab opens immediately on calling Thanks |
For me it usually takes at least 5 seconds for it to open up in the browser (I'm on a MBP15 from 2017) after I start the From my POV it would be great if it always rendered everything in |
Thanks for the update. This is actually how The 5 second pause is there because it takes some time for the sente websockets connection to get established, and messages that get sent before the connection is established fail to reach the client. A smarter thing to do would be to have the client submit a heartbeat message on connection (which might be a little tricky, because I think the client has the same problem) so that the server knows when the client is ready for messages. If nothing is showing up after 5 secs though, that would be a bug (unless the socket is taking that long to set up, which seems unlikely). So please let me know if you continue to see this. I haven't personally had problems with it, but there may be something specific going on. Thanks again |
localhost:5760
doesn't seem to be available until something insite-src
is touched.Teething problems or feature? 馃檪
The text was updated successfully, but these errors were encountered: