-
Notifications
You must be signed in to change notification settings - Fork 4k
Exception while running [email protected] #129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
0 info it worked if it ends with ok Same issue here |
Could you provide more information on what you are doing? This line in particular:
There is no such command in the code I provided And from the folders it says "vue-spa-starter"? Please provide the exact steps you are using after downloading the code from this repo. |
I was able to run and it came with some vulnerabilities, so is ok to update but make sure you run after Hope this helps |
Closing as no additional information on the error was provided. Hopefully it was resolved by the poster. Please reopen if that is not the case. Thanks! |
Hello, I did get the APM-Start to work on another virtual machine. So I think this is releated to some issue installing the nodeJS. I have reinstalled nodejs but still have issue. I don't know where to look next. |
Node version : 12.4.1
npm version 6.13.4
From the log:
0 info it worked if it ends with ok
1 verbose cli [
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'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]
prestart: [email protected]start: [email protected]6 info lifecycle [email protected]
7 verbose lifecycle [email protected]
start: unsafe-perm in lifecycle truestart: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;D:\DeborahK\Angular-GettingStarted-master\APM-Start\node_modules.bin;D:\books\Node js\node js;C:\Program Files\nodejs;C:\Users\Mathod\AppData\Local\Programs\Python\Python37-32\Scripts;C:\Users\Mathod\AppData\Local\Programs\Python\Python37-32;C:\TclDevKit\bin;C:\Ruby200-x64\bin;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files\Intel\WiFi\bin;C:\Program Files\Common Files\Intel\WirelessCommon;D:\books\Node js\node js;C:\Program Files\nodejs;C:\Program Files\Java\jdk-12\bin;C:\Users\Mathod\AppData\Roaming\npm8 verbose lifecycle [email protected]
9 verbose lifecycle [email protected]
start: CWD: D:\DeborahK\Angular-GettingStarted-master\APM-Startstart: Args: [ '/d /s /c', 'ng serve -o' ]10 silly lifecycle [email protected]
11 silly lifecycle [email protected]
start: Returned: code: 1 signal: nullstart: Failed to exec start script12 info lifecycle [email protected]
13 verbose stack Error: [email protected] start:
ng serve -o
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:223:5)
13 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:223:5)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid [email protected]
15 verbose cwd D:\DeborahK\Angular-GettingStarted-master\APM-Start
16 verbose Windows_NT 6.1.7601
17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
18 verbose node v12.14.1
19 verbose npm v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start:
ng serve -o
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Kindly let me know what is the issue?
The text was updated successfully, but these errors were encountered: