'react-scripts' is not recognized as an internal or external command, operable program or batch file

For this error you just have to delete lock file and use command yarn

Resolved by running the following command:

yarn add react-scripts

Just type npm install and after that run npm start. This solved the problem for me.

It's quite common problem. Do the following steps:-

• npm audit The message will be like - 7 vulnerabilities (1 low, 6 high) You will get the vulnerabilities, and now fix it with
• npm audit fix or npm audit fix --force will prompt message like this removed 4 packages, changed 82 packages, and audited 1623 packages in 7s

found 0 vulnerabilities

Problem Solved, Happy Hacking

deleting the node_modules folder and the *.lock file then running npm install in the project directory through the terminal worked. I tried with yarn install and it worked too after removing the mentioned files above.

I just had this issue and this solution worked just fine.

run:

npm install react-scripts

that should solve it... Enjoy!!!

Instead of writing react-scripts start just write npm start.

Just go to the Terminal and on the directory which you start your server. TYPE npm install react-scripts

you will be good to go

Hello I'm learning the MERN stack as well(wise use of quarantine time right? ) Anyways, I'm using WINDOWS 10, and I have the same error as well.

I tried react-scripts start and react-scripts is not recognized as an internal command

I did a bit of googling and found out that you need to npm install react-scripts -g <- notice the -g (stands for global? I think? )

I hope this helps :>

If none of the above solutions works and you have already installed the "react-scripts" package using

npm install react-scripts --save

You can try the below solution to run the application.

You should see the following in your package.json file

"scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
}

The script : "start": "react-scripts start" is linked to the file : nodemon node_modules/react-scripts/scripts/start.js which is used to start the project in the development env

Try to start the project directly using the below commands:

node node_modules/react-scripts/scripts/start.js

or if you have nodemon installed then try

nodemon node_modules/react-scripts/scripts/start.js

Hope this helps :)

One of the causes of this issue is corrupted PATH and the only fix I found for that issue was to (re)install NVM and let the installer take control over the installed Node version when it asks to do so and it will fix the PATH for you. In my case that was the fix.

I found the community answer, which is perfect solution

I had the same issue, resolved by simply running following command in the project root folder -

npm install react-scripts --save

Simply remove node_modules folder and run npm install