vue-cli: Building generated project failed due to vue-cli-service command not found

This error was showing up in my CI environment (CodeShip Ubuntu 14.04). The details below got me unstuck.

With the --production flag (or when the NODE_ENV environment is set to production), npm will not install modules listed in devDependencies."

echo $NODE_ENV
production
npm config get production
true
npm config set -g production false
npm install
npm run build
... all good ...

This will load all dev dependencies including @vue/cli-service which may or may not be desirable depending on what environment you are building for.

If anybody is still facing this issue, i was able to solve it on MacOS by installing globally @vue/cli-service-global.

yarn global add @vue/cli-service-global npm install -g @vue/cli-service-global

Which popped out when running vue serve:

  Command vue serve requires a global addon to be installed.
  Please run yarn global add @vue/cli-service-global and try again.

Hope it helps, Cheers!

I fixed this by :

• uninstalling my current version of node (10.3.0) and installing the latest stable version (8.11.2)
• Uninstalling @ vue/cli package (npm remove -g @ vue/cli )
• and as mentioned by @prinzt installing vue/cli beta-1 (npm install -g @ vue/cli@3.0.0-beta.1)

EDIT: When typing in " @ and vue/cli together as one word, it removes from the text displayed. For clarity, I’ve added a space between the @ sign and the vue/cli. Don’t copy paste these commands unless you plan on removing the space your self.

Note: working on a windows 10 env

This bug could be related to unstable npm installation due to crash in the installation stage: https://github.com/npm/npm/issues/20295

You may close this ticket if you think there is not further issues related to vue-cli

The vue-cli-service script is installed in my local node_modules directory, but the install script does not find it:

$ ./node_modules/\@vue/cli-service/bin/vue-cli-service.js 

  Usage: vue-cli-service <command> [options]

  Commands:

    serve     start development server
    build     build for production
    inspect   inspect internal webpack config
    lint      lint and fix source files

  run vue-cli-service help [command] for usage of a specific command.

$ npm run build

> moo_frontend@1.0.0 build /mnt/partition/home/photoccino/src/apc-tools/moo/frontend
> vue-cli-service build

sh: vue-cli-service: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! moo_frontend@1.0.0 build: `vue-cli-service build`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the moo_frontend@1.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/photoccino/.npm/_logs/2018-04-10T08_15_47_643Z-debug.log

In package.json:

"scripts": {
    "serve": "vue-cli-service serve --open",
    "build": "vue-cli-service build",
    "lint": "vue-cli-service lint"
  },

This error is occuring for me after a fresh vue cli install and running the command : vue create some_project_name

Error: 🚀 Invoking generators... ERROR Error: Failed to resolve plugin: @vue/cli-service Error: Failed to resolve plugin: @vue/cli-service at Creator.resolvePlugins (C:\Users\sheld\AppData\Roaming\npm\node_modules\@vue\cli\lib\Creator.js:303:15) at Creator.create (C:\Users\sheld\AppData\Roaming\npm\node_modules\@vue\cli\lib\Creator.js:146:32) at <anonymous> at process._tickCallback (internal/process/next_tick.js:188:7)

Vue CLI version: Vue CLI v3.0.0-beta.14

on ubuntu I fixed this by:

1. uninstalled my old npm that was installed using apt install apt-get remove npm
2. installed nvm curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.9/install.sh | bash
3. restarted terminal
4. installed latest npm using nvm nvm install --latest-npm
5. reinstall packages as suggested by diachedelic rm -rf node_modules package-lock.json && npm install

Occurs here as well in Windows 10 env with:

• Vue CLI v3.0.0-beta.14
• NPM 6.1.0
• Cmder running git bash OR Cygwin 64 terminal

Extra notes:

• Same Vue CLI and NPM versions work fine in a Linux environment
• node_modules/@vue/cli-service directory exists

Running vue@2.5.17 on This error occurred for me following the use of npm-check-update (ncu v2.14.2):

> landingpages@0.1.0 serve /mnt/sda1/simon/Documents/GitHub/landingpages
> vue-cli-service serve

sh: 1: vue-cli-service: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! landingpages@0.1.0 serve: `vue-cli-service serve`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the landingpages@0.1.0 serve script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/simon/.npm/_logs/2018-10-31T17_53_51_450Z-debug.log

To fix this I ran npm install in the directory . Things worked after this.

+1 But! I do npm run build and again npm run serve. And it’s work!

I think it’s an nvm issue. For me at least switching to a regular node install works, where using nvm gave me the error

I have install

sudo npm install -g @vue/cli-upgrade @vue/cli-service-global

but when I do vue upgrade, it still gives me this:

$ vue upgrade

  Command vue upgrade requires a global addon to be installed.
  Please run yarn global add @vue/cli-upgrade and try again.

🤔 🤔 ❓

{
  "packageManager": "npm",
  "presets": {
    "SFC TS": {
      "useConfigFiles": true,
      "plugins": {
        "@vue/cli-plugin-babel": {},
        "@vue/cli-plugin-typescript": {
          "classComponent": true,
          "tsLint": true,
          "lintOn": [
            "save",
            "commit"
          ],
          "useTsWithBabel": true
        }
      }
    },
    "plain": {
      "useConfigFiles": false,
      "plugins": {}
    }
  },
  "useTaobaoRegistry": false
}

“But! I do npm run build and again npm run serve. And it’s work!”

Same here lol

i have same problem with docker

I also ran into this error when creating a new @vue/cli project (3.0.0-beta.16) with default settings with Node 9.11.1. I resolved the issue using a similar procedure as above:

1. Update to Node 10.4.1 (and npm 6.1.0)
2. Reinstall @vue/cli
3. Do a clean reinstall of project’s node_modules

I’m using n.

I got it working (based on Evan’s hint). Here’s what I did:

1. Upgraded nvm (from v0.32.1 -> v0.33.11)
2. Installed latest node (v10.3.0)
3. Re-installed vue cli (v3.0.0-beta.15)
4. Used GUI to generate new project with same settings as above

Based on that, it’s hard to say whether the ultimate cause of the hangup was the version of NVM or the version of Node, but my guess is that it is a Node version issue.