We help IT Professionals succeed at work.

Failed to exec start script

CarlB3 asked
Angular: 5.0.1 / Angular CLI: 1.5.0 / Node: 8.9.1 / npm: 5.5.1 / Os: win32 x64

I get the below error when executing "npm start" in the terminal/command prompt. Can anyone help me resolve this? I have spent a whole day trying to fix it with no luck.

Here is the scripts section of my package.json

"scripts": {
    "start": "webpack-dev-server --inline --progress --port 8080"

Here is the error

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 npm@5.5.1 3 info using node@v8.9.1 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle angular-io-example@1.0.0~prestart: angular-io-example@1.0.0 6 info lifecycle angular-io-example@1.0.0~start: angular-io-example@1.0.0 7 verbose lifecycle angular-io-example@1.0.0~start: unsafe-perm in lifecycle true 8 verbose lifecycle angular-io-example@1.0.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\cbonsu\Downloads\sample_pro\webpack\node_modules.bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Git\cmd;C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\;C:\Program Files\Microsoft SQL Server\130\DTS\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\ManagementStudio\;C:\WINDOWS\system32\config\systemprofile.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files\dotnet\;C:\Program Files\nodejs\;C:\Users\cbonsu\AppData\Local\Microsoft\WindowsApps;C:\Program Files\nodejs;C:\Program Files\Microsoft VS Code\bin;C:\Users\cbonsu\AppData\Roaming\npm 9 verbose lifecycle angular-io-example@1.0.0~start: CWD: C:\Users\cbonsu\Downloads\sample_pro\webpack 10 silly lifecycle angular-io-example@1.0.0~start: Args: [ '/d /s /c', 10 silly lifecycle 'webpack-dev-server --inline --progress --port 8080' ] 11 silly lifecycle angular-io-example@1.0.0~start: Returned: code: 1 signal: null 12 info lifecycle angular-io-example@1.0.0~start: Failed to exec start script 13 verbose stack Error: angular-io-example@1.0.0 start:  webpack-dev-server --inline --progress --port 8080 13 verbose stack Exit status 1 13 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:280: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. (C:\Program Files\nodejs\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:925:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5) 14 verbose pkgid angular-io-example@1.0.0 15 verbose cwd C:\Users\cbonsu\Downloads\sample_pro\webpack 16 verbose Windows_NT 10.0.15063 17 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start" 18 verbose node v8.9.1 19 verbose npm v5.5.1 20 error code ELIFECYCLE 21 error errno 1 22 error angular-io-example@1.0.0 start: webpack-dev-server --inline --progress --port 8080 22 error Exit status 1 23 error Failed at the angular-io-example@1.0.0 start script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]
Watch Question

Most Valuable Expert 2017
Distinguished Expert 2019

I am going to give you the same answer I have given others.

Angular 5 and CLI 1.5 are still hot from the oven. There are currently (in my view) no major advantages of running of them yet as the updates are mainly in line with Angular's philosophy of smaller, faster etc. The question to ask yourself is what benefit is there wasting time with brand new tech that does not really give you anything new (from a dev perspective) when you could be spending that time building your app and when there is more knowledge on the release available and more of the kinks have been ironed out migrating your code over.

For me I am staying on 4.3 until I see less of these issues coming up with 5.
I've resolved the issue. I've discarded the "npm start" and webpack approach altogether and I'm using angular-cli instead. With angular-cli, calling "ng build --prod" handles everything (aot etc). Behind the scene it uses webpack but it handles all the complications involved so developers don't have to.


It works