Error when I try to execute 'sanity start' after success with 'sanity init'

Question

I am trying to install the Sanity studio and I followed these steps:

npm install --global @sanity/cli

sanity install

sanity init

After the init step, I try to run the next step:

sanity start

but it says:

Run the command again within a Sanity project directory, where "@sanity/core"
is installed as a dependency.
    at D.runCommand (F:/All Node and related projects/node_modules/@sanity/cli/b
in/sanity-cli.js:3254:1345)
    at t.exports (F:/All Node and related projects/node_modules/@sanity/cli/bin/sanity-cli.js:1794:2419)

But when I try to cd into my sanity project directory, it is not even able to recognize sanity, it says:

'sanity' is not recognized as an internal or external command,
operable program or batch file.

Is my dependencies directory structure incorrect? What conditions should be met before you can call sanity start?

THANKS!

Answer 1

I ran into a similar problem wen trying to initialize Sanity. I tried all the above which didn't work form me. As advised above I would run

npm install -g @sanity/cli

then:

sanity init

And I would get the following error:

sanity : The term 'sanity' is not recognized as the name of a cmdlet

The solution I found to this was running the following instead:

npx @sanity/cli init

npx @sanity/cli start

This worked for me like a charm!

Answer 2

The reason why sanity start not working is your command prompt location not same as you installed all sanity packages.

Go back to commend prompt go to the location where sanity is installed and give the commend sanity start it will work .

Answer 3

usually, sanity is set in "studio" directory. In root we install

npm i @sanity/client

and then create "studio" directory in root. cd into "studio"

 cd studio

and inside "studio" directory

 sanity init

This will initialize sanity project inside "studio" directory

If you open the package.json inside "studio", you should have those scripts:

"scripts": {
    "start": "sanity start",
    "build": "sanity build"
  },

Since you are running sanity start in root level, in root package.json file, "start": "sanity start" does not exist that is why you are getting error

To start the sanity server, everytime you should cd studio and then sanity start. Technically you will have two terminals: one for main project development server and second one is for the sanity server

Answer 4

When you run sanity init , it creates a folder for the project (you can choose e-commerce, blog, or no template). cd into that folder that got created and then you can run sanity start

If you can't find where that folder is, you can just create a new one. Sanity is already installed, so you can just go ahead with sanity init

If you're using it with a front end framework, go into the root directory of your project, run the command there, then cd into the created folder then start sanity.

Answer 5

just cd into sanity folder by writing cd sanity and then sanity start

Answer 6

Same issue happened with me then I rechecked whether I'm in the right directory and noticed that I was in the backend directory, then I cd.. and got into the right frontend directory and ran 'npm run dev' and guess what it compiled successfully. So make sure that you are in the right directory.

Answer 7

cd into the sanity folder and yarn dev works for me with the scripts below (you can also use npm run dev)

"scripts": {
    "start": "sanity start",
    "build": "sanity build",
    "dev": "sanity dev"
  },

If I do sanity dev it gives me that error

Answer 8

I encountered this problem sometime, all I did was cd into my sanity folder then run ~ npm install ~ and that solved it for me