vue-cli: vue-cli-service does not run in cmd.exe or Powershell

This was an obscure npm edge case, not related to vue-cli. Was using npm in bash on windows to develop, had to test in cmd.exe. Apparently npm only generates .cmd files for Windows when you run npm install from cmd.exe or Powershell. Deleting node_modules and re-installing from cmd.exe fixes this.

I have such a problem in Windows 10 64bit All is due to --global flag… npm install --global @vue/cli or npm i -g @vue/cli installs node_modules in global route C:\Users\Username\AppData\Roaming\npm But vue-cli-service serve requires to be loaded in current project module locally

So when installing node modules, it is necessary to put cli without -g flag: npm i @vue/cli And then npm serve Now it’s working

Similar problem for me. Deleting node_modules and reinstalling with yarn fixed my problem

npm install --global @vue/cli

I used this command on my bash terminal

And, Then I run vue js app using command npm start And, my terminal shows me and error like,

vue-cli-service serve

'vue-cli-service' is not recognized as an internal or external command, operable program or batch file.

What can i do?

Please, help me,

Happened to me, it turned out when I run npm install --global @vue/cli it installs vue in Administrator’s AppData\Roaming\npm folder instead of the current user’s AppData\Roaming\npm folder.

Manually moving the installed files to the current user AppData\Roaming\npm folder fixed it.

My problem was with Visual Studio 2019 build process. I my case I was able to solve it by providing a more complete path to vue-cli-service in package.json. i.e. `…

“scripts”: { “serve”: “node_modules/.bin/vue-cli-service serve”, “build”: “node_modules/.bin/vue-cli-service build”, “lint”: “node_modules/.bin/vue-cli-service lint” } …` In hindsight probably not of great relevance to this thread, but I got here when looking for a solution to Visual Studio 2019 behaviour with vue projects.

I have had this problem using windows 7, in my case I run npm i and npm run serve in Visual Studio embebed terminal. The problem was fixed when I deleted node_modules folder and run npm i and npm run serve in cmd.

Hm, using git bash on windows isn’t an obscure edge case.

It’s the only way to develop on windows 😃

Oh I see what you are saying, you ran install on cmd and then ran npm command in bash.