-
Notifications
You must be signed in to change notification settings - Fork 416
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
New users must run init twice #372
Comments
Huh, that's strange. Tried on a few different computers now, and can't seem to reproduce this... |
node 8.7.0, macOS Sierra 10.12.6, default browser is Chrome. I can try again (either with the same or a different Google account) on node 8.9.2 if you tell me what files to clear. |
Should be enough with a |
On my machine (which is far from clean) it is reproducible, also on node 8.9.2. Ran I looked a bit more into it
I dug a bit around, added some more console statements: https://github.com/sanity-io/sanity/blob/master/packages/%40sanity/cli/src/actions/login/login.js#L114 Haven't had time to look into the next step, what should have ended the server process. |
Thanks for digging into this! I'm not sure exactly why node is exiting before the promise has been resolved, but it seems unnecessary to wait until the server has closed anyway, so I should be able to refactor this quite easily. Will let you know once I have a new release candidate you can try out. |
@arneke Debugging this is a little hard since I'm not able to reproduce this, but could you try the following:
And see if it has the same issue? |
cli-next worked for me |
Thanks for reporting! |
Definitely minor, but a bit of a buzzkiller for first time users:
mkdir sanity
cd sanity/
npm install -g @sanity/cli
sanity init
Script terminates. Then, if you follow the step-by-step instructions:
sanity start
Huh?
ls -alh
Second attempt works:
sanity init
The text was updated successfully, but these errors were encountered: