Running yarn run sanity-deploy at the root, just hangs

[david-j-davis]

I've just cloned the project, and prepared to deploy the project. Running npm or yarn run sanity-deploy at the root directory just hangs on lerna info Executing command in 1 package: "npm run sanity-deploy"

Expected behavior
This command should run sanity-deploy in the /studio directory without having to go in that directory to deploy.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: OSX 10.14.5
• Browser: Chrome
• Version 74.0.3729

@sanity/cli 0.140.33 (up to date)
@sanity/base 0.140.33 (up to date)
@sanity/cli 0.140.33 (up to date)
@sanity/components 0.140.33 (up to date)
@sanity/core 0.140.32 (up to date)
@sanity/default-layout 0.140.33 (up to date)
@sanity/default-login 0.140.15 (up to date)
@sanity/desk-tool 0.140.33 (up to date)

[kmelve]

Thanks for reporting @david-j-davis! I have just tried to reproduce the issue (pretty much on exactly the same environment), but I don't get the same issue. Now that the deployment will take a couple of minutes because it builds the studio locally before uploading the bundle.

Does it hang if you run sanity deploy from /studio folder? If you run DEBUG=sanity* sanity deploy you'll get a more detailed log as well.

[david-j-davis]

Hi Knut, thanks, it does not hang if I run it from the /studio folder. Just running from the root with `yarn run sanity-deploy` hangs for me.

…

On Fri, Jun 7, 2019 at 10:02 PM Knut Melvær ***@***.***> wrote: Thanks for reporting @david-j-davis <https://github.com/david-j-davis>! I have just tried to reproduce the issue (pretty much on exactly the same environment), but I don't get the same issue. Now that the deployment will take a couple of minutes because it builds the studio locally before uploading the bundle. Does it hang if you run sanity deploy from /studio folder? If you run DEBUG=sanity* sanity deploy you'll get a more detailed log as well. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#102?email_source=notifications&email_token=AA2WB36FNNJK2GEZ2VQOCMLPZM4NPA5CNFSM4HWDC4K2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXHNT4I#issuecomment-500095473>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2WB37CP6GHHD3B7ISNWPLPZM4NPANCNFSM4HWDC4KQ> .