Sanity: Sanity init hanging while 'Resolving latest module versions'

Created on 1 Jun 2019  ·  8Comments  ·  Source: sanity-io/sanity

Upon sanity init and creating a user account for the first time, inputing an output path, the install hands at 'resolving latest module versions.'

Expected behavior
Sanity should continue to install.

Screenshots
Screen Shot 2019-06-01 at 12 26 21 PM

Which versions of Sanity are you using?

@sanity/cli 0.140.30

What operating system are you using?

Mac OS 10.14.5

Which versions of Node.js / npm are you running?

NPM: 6.4.1
Node: 10.15.3

Bug 🔍 Needs Investigation

Most helpful comment

It seems that uninstalling and re-installing the sanity cli fixed the issue.

All 8 comments

Thanks for reporting @david-j-davis! Have you tried this once, or multiple times? This might be a network flake with npm as well.

Hi Knut, I've tried this 3 times now.

On Sat, Jun 1, 2019 at 12:42 PM Knut Melvær notifications@github.com
wrote:

Thanks for reporting @david-j-davis https://github.com/david-j-davis!
Have you tried this once, or multiple times? This might be a network flake
with npm as well.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sanity-io/sanity/issues/1345?email_source=notifications&email_token=AA2WB35D6A25JQ5QQQBM2LDPYLGJDA5CNFSM4HSBEWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXHJCQ#issuecomment-497972362,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2WB3ZPOCUQ3UKGGEWZPZDPYLGJDANCNFSM4HSBEWTA
.

I'm sorry about that. I've tried to reproduce the error without luck, so I'll have to defer this to the team when they're back at office hours on Monday.

There's a slight chance you can find some more useful information if you run:

| => DEBUG=sanity* sanity init

You can also create projects from sanity.io/create btw.

Ok thanks Knut.

On Sat, Jun 1, 2019, 1:00 PM Knut Melvær notifications@github.com wrote:

I'm sorry about that. I've tried to reproduce the error without luck, so
I'll have to defer this to the team when they're back at office hours on
Monday.

There's a slight chance you can find some more useful information if you
run:

| => DEBUG=sanity* sanity init

You can also create projects from sanity.io/create btw.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sanity-io/sanity/issues/1345?email_source=notifications&email_token=AA2WB3Z7DDBIYSEHEM2IHCLPYLIMHA5CNFSM4HSBEWTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXHSNY#issuecomment-497973559,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2WB3YYAERGM244Q63WH7DPYLIMHANCNFSM4HSBEWTA
.

It seems that uninstalling and re-installing the sanity cli fixed the issue.

Great to hear @david-j-davis! We'll be on the lookout for issues like this going forward. You're welcome to join our developer community if you have more questions or need help. Or feel free to reach out on twitter, or post issues here if you find them.

npm uninstall sanity in case this helps

Experiencing this same issue. MacOS 10.14.6, node both 14.9.0 and 12.18.4, npm 6.14.6.

Was this page helpful?
0 / 5 - 0 ratings