npm ERR! code ELIFECYCLE in using NPM RUN SERVE in running PWA Vue.JS 3 Template App on Mac

[deanilvincent]

Version

3.0.3

Node and OS info

Node: v8.12.0, NPM: 6.4.1

Steps to reproduce

I'm having an error while running the newly created pwa template from Vue.JS 3.

The command that I'm using is npm run serve

What is expected?

I'm expecting to run my pwa template.

What is actually happening?

Having error that says

The error says,

npm ERR! code ELIFECYCLE
npm ERR! errno 126
npm ERR! mywebapp@0.1.0 serve: vue-cli-service serve
npm ERR! Exit status 126
npm ERR!
npm ERR! Failed at the mywebapp@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! /var/root/.npm/_logs/2018-09-25T07_17_36_807Z-debug.log

---

Here's the full log from 2018-09-25T07_17_36_807Z-debug.log file

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'serve' ]
2 info using npm@6.4.1
3 info using node@v8.12.0
4 verbose run-script [ 'preserve', 'serve', 'postserve' ]
5 info lifecycle mywebapp@0.1.0preserve: mywebapp@0.1.0
6 info lifecycle mywebapp@0.1.0serve: mywebapp@0.1.0
7 verbose lifecycle mywebapp@0.1.0serve: unsafe-perm in lifecycle true
8 verbose lifecycle mywebapp@0.1.0serve: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/myuser/Documents/AppFolder$
9 verbose lifecycle mywebapp@0.1.0serve: CWD: /Users/myser/Documents/AppFolder/mywebapp
10 silly lifecycle mywebapp@0.1.0serve: Args: [ '-c', 'vue-cli-service serve' ]
11 silly lifecycle mywebapp@0.1.0serve: Returned: code: 126 signal: null
12 info lifecycle mywebapp@0.1.0serve: Failed to exec serve script
13 verbose stack Error: mywebapp@0.1.0 serve: vue-cli-service serve
13 verbose stack Exit status 126
13 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:915:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid mywebapp@0.1.0
15 verbose cwd /Users/myuser/Documents/AppFolder/mywebapp
16 verbose Darwin 17.7.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "serve"
18 verbose node v8.12.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 126
22 error mywebapp@0.1.0 serve: vue-cli-service serve
22 error Exit status 126
23 error Failed at the mywebapp@0.1.0 serve script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 126, true ]

[LinusBorg]

created pwa template from Vue.JS 3.

I assume that means you chose to install the PWA plugin during project creation? What other options did you choose?

You don't provide any details that would allow us to reproduce your scenario.

[michaelmyc]

I am running into similar problems. I can run the build script, but the serve script is malfunctioning.

I created a test project using the default presets, and runs npm run serve immediately after creating the project.
Log here:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'serve' ]
2 info using npm@6.4.1
3 info using node@v10.10.0
4 verbose run-script [ 'preserve', 'serve', 'postserve' ]
5 info lifecycle test@0.1.0~preserve: test@0.1.0
6 info lifecycle test@0.1.0~serve: test@0.1.0
7 verbose lifecycle test@0.1.0~serve: unsafe-perm in lifecycle true
8 verbose lifecycle test@0.1.0~serve: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/michael/projects/test/node_modules/.bin:/home/michael/miniconda3/bin:/home/michael/dotfiles/scripts:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
9 verbose lifecycle test@0.1.0~serve: CWD: /home/michael/projects/test
10 silly lifecycle test@0.1.0~serve: Args: [ '-c', 'vue-cli-service serve' ]
11 silly lifecycle test@0.1.0~serve: Returned: code: 1  signal: null
12 info lifecycle test@0.1.0~serve: Failed to exec serve script
13 verbose stack Error: test@0.1.0 serve: `vue-cli-service serve`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack     at EventEmitter.emit (events.js:182:13)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:182:13)
13 verbose stack     at maybeClose (internal/child_process.js:962:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
14 verbose pkgid test@0.1.0
15 verbose cwd /home/michael/projects/test
16 verbose Linux 4.14.71-1-MANJARO
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "serve"
18 verbose node v10.10.0
19 verbose npm  v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error test@0.1.0 serve: `vue-cli-service serve`
22 error Exit status 1
23 error Failed at the test@0.1.0 serve script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

[michaelmyc]

It seems that EventEmitter is running into some issues. This is probably caused by some upstream changes, since I was able to run the script fine a week or so earlier, and I probably updated something in the mean time.

[deanilvincent]

Yes, @LinusBorg I included the pwa template during the project creation.

[michaelmyc]

So, the problem mysteriously solves itself for me. @deanilvincent Try running npm run serve again. It's probably an upstream issue that is solved now.

[deanilvincent]

Honestly, I've tried it so many times but still, the error persists. I've tried to clean the npm cache, delete node_modules folder then do some package restoration but nothing works.

[haoqunjiang]

Maybe a permission issue. Try sudo?

[deanilvincent]

@sodatea Yup, I already tried it using sudo before posting this question. :(

[ardf69]

Same problem here. I saw the issue is an error ENOSPC. Searching on stackoverflow I found this

https://stackoverflow.com/questions/22475849/node-js-error-enospc

that seems to fix the problem.

[LinusBorg]

@deanilvincent Does @ardf69 's tip help?

[haoqunjiang]

Closing due to inactivity for more than 1 week. Please open a new issue with a reference to this one if you can follow up with more information.