npm start command is not working,Reatc js issue

$ npm start

keeper-app-part-1-starting@1.0.0 start C:\Users\Sukh-work\Desktop\sukh-work\REACT.JS-Work\Keerper-App react-scripts start

npm ERR! code ELIFECYCLE npm ERR! syscall spawn C:\WINDOWS\system32\cmd.exe npm ERR! file C:\WINDOWS\system32\cmd.exe npm ERR! path C:\WINDOWS\system32\cmd.exe npm ERR! errno -4058 npm ERR! keeper-app-part-1-starting@1.0.0 start: react-scripts start npm ERR! spawn C:\WINDOWS\system32\cmd.exe ENOENT npm ERR! npm ERR! Failed at the keeper-app-part-1-starting@1.0.0 start 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! C:\Users\Sukh-work\AppData\Roaming\npm-cache_logs\2020-07-16T20_53_55_112Z-debug.log

---

{ “name”: “keeper-app-part-1-starting”, “version”: “1.0.0”, “keywords”: [], “main”: “src/index.js”, “dependencies”: { “react”: “16.8.6”, “react-dom”: “16.8.6”, “react-scripts”: “^3.4.1” }, “devDependencies”: { “typescript”: “3.3.3” }, “scripts”: { “start”: “react-scripts start”, “build”: “react-scripts build”, “test”: “react-scripts test --env=jsdom”, “eject”: “react-scripts eject” }, “browserslist”: [ “>0.2%”, “not dead”, “not ie <= 11”, “not op_mini all” ], “author”: “”, “license”: “ISC”, “description”: “” }

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:\Users\Sukh-work\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js’, 1 verbose cli ‘start’ 1 verbose cli ] 2 info using npm@6.14.6 3 info using node@v12.18.2 4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ] 5 info lifecycle react-complete-guide@0.1.0~prestart: react-complete-guide@0.1.0 6 info lifecycle react-complete-guide@0.1.0~start: react-complete-guide@0.1.0 7 verbose lifecycle react-complete-guide@0.1.0~start: unsafe-perm in lifecycle true 8 verbose lifecycle react-complete-guide@0.1.0~start: PATH: C:\Users\Sukh-work\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\Sukh-work\Desktop\sukh-work\REACT.JS-Work\burgerApp-part-1\node_modules.bin;C:\Users\Sukh-work\bin;C:\Users\Sukh-work\AppData\Local\Programs\Git\mingw64\bin;C:\Users\Sukh-work\AppData\Local\Programs\Git\usr\local\bin;C:\Users\Sukh-work\AppData\Local\Programs\Git\usr\bin;C:\Users\Sukh-work\AppData\Local\Programs\Git\usr\bin;C:\Users\Sukh-work\AppData\Local\Programs\Git\mingw64\bin;C:\Users\Sukh-work\AppData\Local\Programs\Git\usr\bin;C:\Users\Sukh-work\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\C;C:\Users\Sukh-work\AppData\Local\Programs\Git\Users\Ivana\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Python 3.7;C:\Program Files\nodejs;%NVM_HOME%;%NVM_SYMLINK%;C:\Users\Sukh-work\AppData\Local\Microsoft\WindowsApps;C:\Users\Sukh-work\AppData\Local\hyper\app-3.0.2\resources\bin;C:\Users\Sukh-work\AppData\Local\Programs\Git\cmd;C:\ProgramData\Sukh-work\atom\bin;C:\Users\Sukh-work\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\Sukh-work\AppData\Roaming\npm;C:\Users\Sukh-work\AppData\Local\Programs\Git\usr\bin\vendor_perl;C:\Users\Sukh-work\AppData\Local\Programs\Git\usr\bin\core_perl 9 verbose lifecycle react-complete-guide@0.1.0~start: CWD: C:\Users\Sukh-work\Desktop\sukh-work\REACT.JS-Work\burgerApp-part-1 10 silly lifecycle react-complete-guide@0.1.0~start: Args: [ ‘/d /s /c’, ‘node scripts/start.js’ ] 11 info lifecycle react-complete-guide@0.1.0~start: Failed to exec start script 12 silly lifecycle react-complete-guide@0.1.0~start: Returned: code: -4058 signal: null 13 info lifecycle react-complete-guide@0.1.0~start: Failed to exec start script 14 verbose stack Error: react-complete-guide@0.1.0 start: node scripts/start.js 14 verbose stack spawn C:\WINDOWS\system32\cmd.exe ENOENT 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19) 14 verbose stack at onErrorNT (internal/child_process.js:469:16) 14 verbose stack at processTicksAndRejections (internal/process/task_queues.js:84:21) 15 verbose pkgid react-complete-guide@0.1.0 16 verbose cwd C:\Users\Sukh-work\Desktop\sukh-work\REACT.JS-Work\burgerApp-part-1 17 verbose Windows_NT 10.0.18363 18 verbose argv “C:\Program Files\nodejs\node.exe” “C:\Users\Sukh-work\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js” “start” 19 verbose node v12.18.2 20 verbose npm v6.14.6 21 error code ELIFECYCLE 22 error syscall spawn C:\WINDOWS\system32\cmd.exe 23 error file C:\WINDOWS\system32\cmd.exe 24 error path C:\WINDOWS\system32\cmd.exe 25 error errno ENOENT 26 error react-complete-guide@0.1.0 start: node scripts/start.js 26 error spawn C:\WINDOWS\system32\cmd.exe ENOENT 27 error Failed at the react-complete-guide@0.1.0 start script. 27 error This is probably not a problem with npm. There is likely additional logging output above. 28 verbose exit [ 1, true ]

[oseisaac]

Thank you every one for trying to help me, i found the error , it was with my cmd.exe file,it was missing in my system ,that’s why my dependencies was not able to update.

How did you fix the issue, Im experiencing the same thing ?

[lveillard]

@Sukhvir2104 same for me, I have the same issue, all my commands get “/d /s /c” in the begining and they obviously don’t work.

If only everyone telling “is ok I solved it” just wrote also what they do to solve it… haha hope you can tell us 😃