-
Notifications
You must be signed in to change notification settings - Fork 2k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Onboarding: No indication of URL in the console until you first try loading Calypso in the browser #467
Comments
@nb is this done with: Or is there anything left? |
I think @apeatling wants us to have a message earlier, probably we can just include the hostname in the boot message. |
@mtias You don't get that message until after you have hit the browser. |
Right :) |
Initially I was confused too, but you get the ready message regardless of the browser. The compiling is happening, and if you don't do anything, the URL will appear. The message:
Appears only in the case you hit the browser before it's "Ready!"... which shouldn't happen, since we don't show the message until that moment... and that's why the message is shown. ;) So... I actually would not show the URL before, since before it's shown, it's not ready yet! See #1039 that already fixed the flow adding the wait message. :) |
@folletto Maybe what is needed is an opening message explaining what is going to happen before compilation begins? Something like
|
The message is already there (#1039 merged it): This issue was older than that. :D |
Once I have built Calypso, until I try loading it in the browser the only indication I get in the console is:
wp-calypso booted in 680ms - port: 3000
'It doesn't tell me what URL to go to. Unless I know that, I wouldn't have any idea unless I read the readme, and we know a lot of people won't be doing that.
Of course once I load it, because I know the URL it shows it in the console:
Compiling assets... Wait until you see READY! and then try http://calypso.localhost:3000/ again.
this information needs to be shown sooner, without the need to try it in the browser first. /cc @nb
The text was updated successfully, but these errors were encountered: