react-scripts is not recognized as an internal or external command

Question

I ve got a maven project  within which is JavaScript project cloned as a git sub-module  So the directory structure looks like mavenapp src main javascript  npm project files  Inside my package json  the test looks like this   quot test quot    quot react-scripts test --env jsdom quot    but when I try to run npm test  it says   react-scripts  is not recognized as an internal or external command   Interestingly  when I clone the javascript project independently I don t get this error  I ve tried re-running npm install  NPM version  5 5 1 Node js version  9 3 0

User · Answer

This is how I fix it

Check and Update the path variable (See below on how to update the path variable)
Delete node_modules and package-lock.json
run npm install
run npm run start

if this didn't work, try to install the nodejs and run repair

or clean npm cache npm cache clean --force

To update the path variable

press windows key
Search for Edit the system environmental variable
Click on Environment Variables...
on System variable bottom section ( there will be two section )
Select Path variable name
Click Edit..
Check if there is C:\Program Files\nodejs on the list, if not add this

User · Answer

If react-scripts is present in package json  then just type this command npm install  If react-scripts is not present in package json  then you probably haven t installed it  To do that  run  npm install react-scripts --save

User · Answer

I have tried many of the solutions to this problem found on line  but in my case nothing worked except for reinstalling NVM for Windows  which I am using to manage multiple Node versions   In the installer  it detects installed Node versions and asks the user if they wish for NVM to control them  I said yes and NVM fixed all PATH issues  As a result  things worked as before  This issue may have multiple causes  but corrupted PATH is definitely one of them and  re installing NVM fixes PATH

User · Answer

first run  npm ci  then  npm start

User · Answer

For me  I just re-installed the react-scripts instead of react-scripts --save

User · Answer

It is an error about react-scripts file missing in your node modules  directory at the time of installation  Check your react-script dependency is avaliable or not in package json  If not available then add it manually via  npm install react-scripts --save

User · Answer

For Portable apps change      package json   as follows   scripts          start    node node modules  bin react-scripts start        build    node node modules  bin react-scripts build        test    node node modules  bin react-scripts test        eject    node node modules  bin react-scripts eject

User · Answer

To rectify this issue follow the following steps  run npm install then run npm start  This worked fine for me

User · Answer

had similar issue   i used yarn to fix it  i noticed that react-scripts was not found in my node modules so i decided to download it with npm but i seem to be failing too  so i tried yarn   yarn add react-scripts  and that solved the nightmare  Hope this work for you as well  Happy debuging folks

User · Answer

I uninstalled my Node js and showed hidden files   Then  I went to C  Users yourpcname AppData Roaming  and deleted the npm and npm-cache folders   Finally  I installed a new version of Node js

User · Answer

In my case  the problem had to do with not having enough file permissions for some files the react-scripts package installation was going to write to  What solved it was running git bash as an administrator and then running npm install --save react-scripts again

User · Answer

Running these commands worked for me  npm cache clean --force npm rebuild npm install

User · Answer

In my situation  some problems happened with my node package  So I run npm audit fix and it fixed all problems

User · Answer

In my case   I edited my files on Linux where I had node v14 0 5 installed  when I rebooted to Windows where I had node v14 0 3 I got the same error  So I updated the node version on windows and all went fine for me

User · Answer

This worked for me   Go to the project folder in CLI and type npm install Go for a similar command if using yarn etc   Then type npm start if you are using Npm  Go for a similar command if using yarn etc   The file starts working

User · Answer

Faced the same problem  although I am using yarn    The following worked for me   yarn install  yarn start

User · Answer

When I make a new project using React  to install the React modules I have to run  npm install   PowerShell  from within the new projects ClientApp folder  e g   C  Users Chris source repos HelloWorld2 HelloWorld2 ClientApp    The  NET core WebApp with React needs to have the React files installed in the correct location for React commands to work properly

User · Answer

Running the npm update command solved my problem

User · Answer

This is rather old question but this might be of some help for future reference  Delete node modules folder and run npm install again  Worked for me

User · Answer

react-scripts is not recognized as an internal or external command is related to npm   I would update all of my dependencies in my package json files to the latest versions in both the main directory and client directory if applicable  You can do this by using an asterisk     instead of specifying a specific version number in your package json files for your dependencies   For Example    dependencies          body-parser             express             mongoose             react             react-dom             react-final-form             react-final-form-listeners             react-mapbox-gl             react-redux             react-responsive-modal              I would then make sure any package-lock json were deleted and then run npm install and yarn install in both the main directory and the client directory as well if applicable   You should then be able to run a yarn build and then use yarn start to run the application

User · Answer

Try  rm -rf node modules  amp  amp  npm install  Wiping node modules first  often tends to fix a lot of weird  package related issues like that in Node

[javascript] 'react-scripts' is not recognized as an internal or external command

This is how I fix it

To update the path variable

Examples related to javascript

Examples related to node.js

Examples related to maven