Reputation: 31
npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] start: `react-scripts start` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] 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! /home/josh/.npm/_logs/2020-08-21T19_28_35_521Z-debug.log
Edit:
package.json
{
"name": "todos-clone-app",
"version": "0.1.0",
"private": true,
"dependencies": {
"@testing-library/jest-dom": "^4.2.4",
"@testing-library/react": "^9.5.0",
"@testing-library/user-event": "^7.2.1",
"react": "^16.13.1",
"react-dom": "^16.13.1",
"react-scripts": "3.4.3",
"webpack-dev-server": "^3.11.0"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": "react-app"
},
"browserslist": {
"production": [ ">0.2%", "not dead", "not op_mini all" ],
"development": [ "last 1 chrome version", "last 1 firefox version", "last 1 safari version" ]
}
}
Upvotes: 1
Views: 7793
Reputation: 1796
For all future latest nodejs versions you need to modify your package.json, as below for Reactjs to run in the browser, only if you face issues running npm start using the default added, start script command Update your script command as below:
"scripts": { "start": "react-scripts start --openssl-legacy-provider",
Upvotes: 0
Reputation: 41
In my case, it was because of not being in the right folder.
Generally, I create a folder and go to Vs code to open it for typing create-react-app "folder name"
to the console.
The problem was I was trying to npm start
in parent folder instead of "folder name".
All you have to do is:
cd folder_name
npm start
Upvotes: 3
Reputation: 153
Try deleting your node_modules
directory and package-lock.json
file. Then run npm install
.
Upvotes: 2