facebook / create-react-app

Set up a modern web app by running one command.
https://create-react-app.dev
MIT License
102.74k stars 26.86k forks source link

Recently I have Installed SSD to my Laptop with hdd. My React App are Not working Showing Errors #12355

Open avinashbt opened 2 years ago

avinashbt commented 2 years ago

Windows PowerShell Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\Users\Dell\Desktop\Mobile Apps\Cloud-Chain-Dashboard-FE> npm start

app-frontend@0.1.0 start npm run start:localhost

app-frontend@0.1.0 start:localhost cross-env REACT_APP_ENVIRONMENT=localhost react-scripts start

'react-scripts' is not recognized as an internal or external command, operable program or batch file. throw er; // Unhandled 'error' event ^

Error: spawn react-scripts ENOENT at notFoundError (C:\Users\Dell\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:6:26) at verifyENOENT (C:\Users\Dell\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:40:16) at ChildProcess.cp.emit (C:\Users\Dell\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:27:25) Emitted 'error' event on ChildProcess instance at: at ChildProcess.cp.emit (C:\Users\Dell\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:30:37) at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) { code: 'ENOENT', errno: 'ENOENT', syscall: 'spawn react-scripts', path: 'react-scripts', spawnargs: [ 'start' ] } PS C:\Users\Dell\Desktop\Mobile Apps\Cloud-Chain-Dashboard-FE> npm install -g npm@latest

changed 14 packages, and audited 202 packages in 10s

11 packages are looking for funding run npm fund for details

found 0 vulnerabilities PS C:\Users\Dell\Desktop\Mobile Apps\Cloud-Chain-Dashboard-FE> npm start

app-frontend@0.1.0 start npm run start:localhost

app-frontend@0.1.0 start:localhost cross-env REACT_APP_ENVIRONMENT=localhost react-scripts start

'react-scripts' is not recognized as an internal or external command, operable program or batch file. throw er; // Unhandled 'error' event ^

Error: spawn react-scripts ENOENT at notFoundError (C:\Users\Dell\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:6:26) at verifyENOENT (C:\Users\Dell\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:40:16) at ChildProcess.cp.emit (C:\Users\Dell\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:27:25) at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) Emitted 'error' event on ChildProcess instance at: at ChildProcess.cp.emit (C:\Users\Dell\AppData\Roaming\npm\node_modules\cross-env\node_modules\cross-spawn\lib\enoent.js:30:37) at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12) { code: 'ENOENT', errno: 'ENOENT', syscall: 'spawn react-scripts', path: 'react-scripts', spawnargs: [ 'start' ] } PS C:\Users\Dell\Desktop\Mobile Apps\Cloud-Chain-Dashboard-FE> npm install npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: app-frontend@0.1.0 npm ERR! Found: react@17.0.1 npm ERR! node_modules/react npm ERR! react@"17.0.1" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^16.2.0" from react-otp-input@2.4.0 npm ERR! node_modules/react-otp-input npm ERR! react-otp-input@"^2.4.0" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See C:\Users\Dell\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\Dell\AppData\Local\npm-cache_logs\2022-05-03T10_42_20_847Z-debug-0.log PS C:\Users\Dell\Desktop\Mobile Apps\Cloud-Chain-Dashboard-FE>

gustta03 commented 2 years ago

maybe this can help

https://github.com/facebook/create-react-app/issues/2436#issuecomment-334656060