-
Notifications
You must be signed in to change notification settings - Fork 6.9k
Error on npm start - Exit status 1 #292
Comments
let me try that again. my package.json looks like this
} |
Did you install nodejs ? Try to clone the nodejs then try to start with |
yes thanks |
In my own project I am able to run protractor (without karma) from the command line if I first start selenium using webdriver-manager start |
I'm getting the same issue |
L uydwfml
|
L uydwfml I'm getting the same issue — |
hi, I fixed changing the port in the package,json file orginal fixed if you have installed and running IIS or some automatic server that use the localhost port 8000 can block the node server. |
Same issue here. Changing the port number does not help in my case. Any further suggestions? |
It maybe because another app is using the same port or you prematurely stop the application, if your on a linux machine, verify if the port is running lsof -i:port check if the running application is npm, now try to terminate it by kill -9 npm start It should be working now. |
gays,try these two commands: |
All dependencies and tools have been updated recently and this is hopefully not an issue any more. There are also some good suggestions above, that might help in certain cases (although this is a generic error and can be caused by several things). |
I also encountered this problem, and my situation is that the port was occupied. |
|
I downloaded angular-seed to my computer. Then opened the command prompt to the root folder. npm install worked ok. I was also able to get jasmine tests to work OK. But not protractor. when I type npm start I get this.
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart [email protected]
6 verbose unsafe-perm in lifecycle true
7 info start [email protected]
8 verbose unsafe-perm in lifecycle true
9 info [email protected] Failed to exec start script
10 verbose stack Error: [email protected] start:
http-server -a localhost -p 8000 -c-1
10 verbose stack Exit status 1
10 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:213:16)
10 verbose stack at EventEmitter.emit (events.js:110:17)
10 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
10 verbose stack at ChildProcess.emit (events.js:110:17)
10 verbose stack at maybeClose (child_process.js:1015:16)
10 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
11 verbose pkgid [email protected]
12 verbose cwd D:\Projects\AngularSeed
13 error Windows_NT 6.1.7601
14 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
15 error node v0.12.6
16 error npm v2.11.2
17 error code ELIFECYCLE
18 error [email protected] start:
http-server -a localhost -p 8000 -c-1
18 error Exit status 1
19 error Failed at the [email protected] start script 'http-server -a localhost -p 8000 -c-1'.
19 error This is most likely a problem with the angular-seed package,
19 error not with npm itself.
19 error Tell the author that this fails on your system:
19 error http-server -a localhost -p 8000 -c-1
19 error You can get their info via:
19 error npm owner ls angular-seed
19 error There is likely additional logging output above.
20 verbose exit [ 1, true ]
The text was updated successfully, but these errors were encountered: