Building generated project failed due to vue-cli-service command not found
See original GitHub issueI created a new Vue project using the vue create
command. I managed to build it properly on my MacOS platform, but on a CentOS 6.9 platform the build fails with the following error message:
sh: vue-cli-service: command not found
I found a workaround by modifying package.json
as follows:
"scripts": {
"serve": "./node_modules/\\@vue/cli-service/bin/vue-cli-service.js serve --open",
"build": "./node_modules/\\@vue/cli-service/bin/vue-cli-service.js build",
"lint": "./node_modules/\\@vue/cli-service/bin/vue-cli-service.js lint"
},
Version
3.0.0-beta.6
Reproduction link
This is random link, do not open! I cannot reproduce in these places. https://jsfiddle.net/chrisvfritz/50wL7mdz/
Steps to reproduce
Install latest npm, latest vue-cli and try to build a Vue project in CentOS 6.9
What is expected?
The build should succeed
What is actually happening?
$ 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-10T06_37_11_606Z-debug.log
$ cat /home/photoccino/.npm/_logs/2018-04-10T06_37_11_606Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
2 info using npm@5.8.0
3 info using node@v8.11.1
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle moo_frontend@1.0.0~prebuild: moo_frontend@1.0.0
6 info lifecycle moo_frontend@1.0.0~build: moo_frontend@1.0.0
7 verbose lifecycle moo_frontend@1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle moo_frontend@1.0.0~build: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/mnt/partition/home/photoccino/src/apc-tools/moo/frontend/node_modules/.bin:/usr/local/bin:/usr/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/photoccino/bin
9 verbose lifecycle moo_frontend@1.0.0~build: CWD: /mnt/partition/home/photoccino/src/apc-tools/moo/frontend
10 silly lifecycle moo_frontend@1.0.0~build: Args: [ '-c', 'vue-cli-service build' ]
11 info lifecycle moo_frontend@1.0.0~build: Failed to exec build script
12 verbose stack Error: moo_frontend@1.0.0 build: `vue-cli-service build`
12 verbose stack spawn ENOENT
12 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack at emitTwo (events.js:126:13)
12 verbose stack at ChildProcess.emit (events.js:214:7)
12 verbose stack at maybeClose (internal/child_process.js:925:16)
12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
13 verbose pkgid moo_frontend@1.0.0
14 verbose cwd /mnt/partition/home/photoccino/src/apc-tools/moo/frontend
15 verbose Linux 2.6.32-131.17.1.el6.x86_64
16 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
17 verbose node v8.11.1
18 verbose npm v5.8.0
19 error file sh
20 error code ELIFECYCLE
21 error errno ENOENT
22 error syscall spawn
23 error moo_frontend@1.0.0 build: `vue-cli-service build`
23 error spawn ENOENT
24 error Failed at the moo_frontend@1.0.0 build script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]
Issue Analytics
- State:
- Created 5 years ago
- Reactions:50
- Comments:36 (6 by maintainers)
Top Results From Across the Web
error "vue-cli-service: command not found" when running a ...
Vue-cli should not be in your package.json as a dependency (not even in dev-dependencies) because it is used only to generate a new...
Read more >Netlify build error: vue-cli-service not found - Hao's learning log
I recently created a project using Vue CLI 3, and after got the project set up to a basic state I decided to...
Read more >Build Targets - Vue CLI
When you run vue-cli-service build , you can specify different build targets via the --target option. This allows you to use the same...
Read more >Vue: Deploy failed because of "npm run build" not working?
Hi there, I'm currently working on a Vue app and to check if everything's working fine in “the real world”, I deployed the...
Read more >@vue/cli-service | Yarn - Package Manager
@vue/cli-service. owner vuejs4.2mMIT5.0.8TS vulns 0 vulnerabilities. local service for vue-cli projects. vue, cli. readme. @vue/cli-service.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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."
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
:Hope it helps, Cheers!