'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:

"test": "react-scripts test --env=jsdom",

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

when using create react app. sometimes the top fix might not work. you must then look at other solutions like manullay checking the versions of "react scripts" in package.json and package-lock.json and then reinstall node module using npm install — AKLI JOSHUA Eric Yao
– AKLI JOSHUA Eric Yao, Commented Aug 10 at 22:49

double-beep · Accepted Answer · 2021-01-26 21:10:05Z

343

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

edited Jan 26, 2021 at 21:10

double-beep

5,67019 gold badges43 silver badges50 bronze badges

answered Apr 2, 2018 at 4:30

Yogesh Borad

4,7251 gold badge20 silver badges18 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Rosdi Kasim Over a year ago

DO NOT do this, this could cause issues with other projects... you should NOT install react-scripts globally like this. Refer here: github.com/facebook/create-react-app/issues/…

Yogesh Borad Over a year ago

@RosdiKasim After read your comment, I have realized my error. Now, I have changed the command for the specific project instead of globally(-g).

Giox Over a year ago

Nothing changes for me, still the same error. Running "npm install react-scripts --save" even if succesful doesn't create any folder react-scripts in npm_modules folder. I'm on Windows10

Janac Meena Over a year ago

If using Yarn V2, or Create React-App, you just need to run yarn install before yarn start.

John Zenith Over a year ago

Run yarn install or npm install to fix the issue as this was sufficient in my case.

|

Hadi Mir · Accepted Answer · 2021-01-27 05:50:40Z

187

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

edited Jan 27, 2021 at 5:50

answered Jan 28, 2019 at 14:12

Hadi Mir

5,1752 gold badges33 silver badges34 bronze badges

5 Comments

Serob Over a year ago

What if I have it in my package.json and also install it, but face the same problem?

Hadi Mir Over a year ago

@Serob_b Sometimes I also have same problem in that case i just run "npm install" and it solves the problem. or you can always delete the node_modules folder by typing rm "-rf node_modules" in terminal and then run "npm install". hope this helps

GermanJablo Over a year ago

This is the complete answer

Yusuf Over a year ago

still not working

Muhammad Luqman Nov 24 at 9:50

Running "npm install react-scripts@latest" resolved my issue.

double-beep · Accepted Answer · 2021-01-26 21:09:35Z

86

Try:

rm -rf node_modules && npm install

Wiping node_modules first, often tends to fix a lot of weird, package related issues like that in Node.

edited Jan 26, 2021 at 21:09

double-beep

5,67019 gold badges43 silver badges50 bronze badges

answered Dec 21, 2017 at 18:26

Jonny Asmar

2,00014 silver badges17 bronze badges

6 Comments

TheRealJimShady Over a year ago

yes I have... no difference... For now I've had to just removed the submodule and just paste it in manually.

Jonny Asmar Over a year ago

Hmm, you're not seeing any errors logged from your npm install are you? Try to run an npm install -f and see if anything changes. Could be another package that's failing to install and blocking create-react-app from installing completely. Forcing an npm install with -f, btw, is never a complete solution.... just a troubleshooting step. If anything changes after you run that, then you know there is something wrong with one of the packages.

Jonny Asmar Over a year ago

Additionally, you may want to verify that you have a file at javascript/node_modules/.bin/react-scripts. If not, there could be several different causes for this, which include permissions issues, OS restrictions on creating symlinks (everything in node_moduels/.bin is a symlink generated on install. Could also just be that you don't have react-scripts installed... try running npm install --save react-scripts and see if that helps.

A-S Over a year ago

Moving from MacOS to Windows (Dropbox synced all the node_modules folder) - only deleting the folder and re-installing solved it

Jonny Asmar Over a year ago

Yep -- thats what the above command does. Your symptom was likely due to a number of packages that perform conditional install procedures per OS. Linux, Mac, & Windows have quite a few discrepancies with a lot of fundamental project dependencies.

|

crispengari · Accepted Answer · 2021-01-26 21:20:08Z

43

Running these commands worked for me:

npm cache clean --force
npm rebuild
npm install

edited Jan 26, 2021 at 21:20

answered Nov 26, 2020 at 16:48

crispengari

9,5518 gold badges59 silver badges69 bronze badges

3 Comments

Jason Over a year ago

npm install => npm rebuild worked for me. I've gotten this error with 'react-scripts' and 'next'. It seems to happen after I delete the node_modules folder and go back to the project at a later date.

Joe Sadoski Over a year ago

Worked for me, but npm cache clean --force was not necessary (node v14.17.3, npm 6.14.13). I did use npm cache verify instead. I'm not sure if whether or not this had an effect.

user8234870 Over a year ago

@crispengari please explain how these command works and fix the problem

Raskul · Accepted Answer · 2024-01-30 13:22:52Z

29

2024 answer: simply remove node_modules folder and run

npm install

or:

yarn

(depends on you're using npm or yarn)

it worked for me!

no need to do more!!!

It waste a lot of my time until I discover this, I got headache...

edited Jan 30, 2024 at 13:22

answered Apr 16, 2022 at 0:32

Raskul

2,3071 gold badge22 silver badges31 bronze badges

1 Comment

TheRealJimShady Over a year ago

how's your head now @Raskul?

Nguyen Duc Thanh · Accepted Answer · 2019-02-27 15:22:46Z

19

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

answered Feb 27, 2019 at 15:22

Nguyen Duc Thanh

1901 silver badge5 bronze badges

1 Comment

Wakas Abbasid Over a year ago

This seems the best answer so far. I migrated my code from Macbook to a PC and was unable to run my react project. "npm audit fix" solved it instantly.

KushalSeth · Accepted Answer · 2021-05-03 01:04:33Z

18

To avoid this issue to re-occur or you face this issue whenever anyone downloads your project fresh.

It's better to add this in dev dependencies using this command:

npm install react-scripts --save-dev

It will get added like this.

  "devDependencies": {
    "react-scripts": "^4.0.3"
  }

Do Commit and push your code.

answered May 3, 2021 at 1:04

KushalSeth

5,0461 gold badge41 silver badges39 bronze badges

2 Comments

Musarrof Aug 19 at 22:50

I tried all of this above but this command is working fine for me, Thanks

Ayooluwa Oladele Oct 27 at 0:49

Thank you. I tried even chatGPT but none worked. This works just perfectly

cela · Accepted Answer · 2020-06-03 20:16:02Z

15

Faced the same problem, although I am using yarn.

The following worked for me:

yarn install 
yarn start

edited Jun 3, 2020 at 20:16

cela

2,5203 gold badges26 silver badges46 bronze badges

answered Jun 3, 2020 at 15:37

Pope Francis

5858 silver badges9 bronze badges

Comments

double-beep · Accepted Answer · 2021-01-26 21:11:29Z

12

Running the npm update command solved my problem.

edited Jan 26, 2021 at 21:11

double-beep

5,67019 gold badges43 silver badges50 bronze badges

answered Feb 16, 2020 at 5:10

Miraj Khandaker

1,13214 silver badges11 bronze badges

Comments

Community · Accepted Answer · 2022-08-17 14:50:18Z

10

For Portable apps change

package.json

as follows

"scripts": {

    "start": "node node_modules/react-scripts/bin/react-scripts start",
    "build": "node node_modules/react-scripts/bin/react-scripts build",
    "test": "node node_modules/react-scripts/bin/react-scripts test",
    "eject": "node node_modules/react-scripts/bin/react-scripts eject"
  }

edited Aug 17, 2022 at 14:50

CommunityBot

11 silver badge

answered Feb 7, 2020 at 17:37

smamran

7872 gold badges14 silver badges23 bronze badges

1 Comment

Tanveer Badar Over a year ago

Not sure why it happened, but I was able to provide explicit path to the script and it worked fine.

Muhammad Ali · Accepted Answer · 2023-03-16 11:17:24Z

10

React Scripts Not Recognized as internal/external script

Step by Step Solution:

Open Project root folder (where your package.json is located) in cmd.
Run this script.
```
npm install react-scripts
```
Clear your npm cache if necessary.

Still Not Resolved?

try to delete your node_modules and package-lock.json (not package.json) files, re-run npm install and restart your IDE.

rd /s /q "node_modules"
del package-lock.json
del -f yarn.lock

# to clean npm cache
npm cache clean --force

# to install packages
npm install

Make sure to restart your IDE and dev server if the error persists.

Hope it helps.

answered Mar 16, 2023 at 11:17

Muhammad Ali

1,3783 gold badges20 silver badges23 bronze badges

1 Comment

jin bai Over a year ago

First principle thinking👍

Salman · Accepted Answer · 2020-08-08 18:05:31Z

8

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

answered Aug 8, 2020 at 18:05

Salman

1,04813 silver badges14 bronze badges

Comments

Paa Solo · Accepted Answer · 2021-02-12 00:06:50Z

8

To rectify this issue follow the following steps

run npm install
then run npm start

This worked fine for me

answered Feb 12, 2021 at 0:06

Paa Solo

911 silver badge3 bronze badges

Comments

Hessah · Accepted Answer · 2021-10-14 09:28:19Z

react-scripts should be listed as a dependency when you run npx create-react-app your-app, but for some reason, it gets this error. I will list some steps that I followed that may help you fix this error:

First, check at your React package.json if there is react-scripts or not: for example, you should see:

"dependencies": {
    ...
    "react-scripts": "4.0.3",
    ...
  },

If it's already there, now try to re-install your dependencies with npm i

If you still get the same error, try to remove your node_modules with rm -rf node_modules/, then re-install your dependencies with npm i

BUT if the package react-scripts wasn't in your package.json file, you should install it by your package manager like: npm i react-scripts then try to start your app with npm start

raghurajj · Accepted Answer · 2021-03-01 03:22:07Z

7

I faced the same issue. I solved it using npm audit fix --force

answered Mar 1, 2021 at 3:22

raghurajj

831 silver badge5 bronze badges

2 Comments

domdaviesdev Over a year ago

npm audit fix --force worked for me after trying a number of solutions on this page. I'm doing the wes bos react course and was unable to even finish the first video with this error. Windows 10, VS Code, Node v14.17.4, npm 7.20.5

Mubasher Ali Over a year ago

don't use this command it will break your code if you have vulnerable packages

double-beep · Accepted Answer · 2021-01-26 21:12:52Z

6

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.

edited Jan 26, 2021 at 21:12

double-beep

5,67019 gold badges43 silver badges50 bronze badges

answered Apr 2, 2018 at 8:25

Sandro Cagara

351 silver badge1 bronze badge

1 Comment

Phani Rithvij Over a year ago

This is not a solution really.

Mubasher Ali · Accepted Answer · 2021-03-30 16:30:44Z

5

I had the same issue. I did everything which suggested here. but nothing worked. I had installed react-scripts in my node_modules also used cache but all in vain. then I just npx create-react-app and moved all my code into this new folder and all worked.

npx create-react-app myapp

answered Mar 30, 2021 at 16:30

Mubasher Ali

5426 silver badges14 bronze badges

1 Comment

Muhammad Ali Over a year ago

Exactly, this method works.

Chadrack Kyungu · Accepted Answer · 2022-05-02 09:06:35Z

4

As for me i managed to fix this issue by install this :

npm audit fix --force

and it work after that.

answered May 2, 2022 at 9:06

Chadrack Kyungu

635 bronze badges

Comments

Ahmedakhtar11 · Accepted Answer · 2022-10-29 05:52:56Z

4

This is not recommended, so plz don't down arrow, but for troubleshooting..

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.

edited Oct 29, 2022 at 5:52

answered Dec 19, 2018 at 3:15

Ahmedakhtar11

1,58819 silver badges9 bronze badges

2 Comments

Dana Woodman Over a year ago

This is bad advice. Using * for your version numbers is problematic because it could cause different versions of packages being installed on different systems. Use locked version numbers and update them as needed

Ahmedakhtar11 Over a year ago

Yea things could totally go wrong here for production purposes, but just an idea for testing purposes.

Korotkevich · Accepted Answer · 2021-12-12 11:35:36Z

3

Use git bash or windows cmd with admin rights to run npm install while fixing this issue, running these commands inside the editor's terminals doesn't help.

answered Dec 12, 2021 at 11:35

Korotkevich

619 bronze badges

Comments

Ahsan Alamgir · Accepted Answer · 2024-09-05 16:19:30Z

3

I had the same issue but it was working previously. npm install did not work so I had to run

npm install -g react-scripts

This solved my problem after installing globally. Thanks.

answered Sep 5, 2024 at 16:19

Ahsan Alamgir

591 bronze badge

Comments

Emir Mamashov · Accepted Answer · 2021-01-26 17:49:56Z

2

first run:

npm ci

then:

npm start

answered Jan 26, 2021 at 17:49

Emir Mamashov

1,16810 silver badges14 bronze badges

Comments

rashid_m · Accepted Answer · 2023-03-02 11:10:05Z

1

Here is what worked for me,

did npm install and that didn't fix it so I simply disabled windows defender firewall and then made a fresh cloning of the repo followed by npm start. That's it!

answered Mar 2, 2023 at 11:10

rashid_m

565 bronze badges

Comments

Adim Victor · Accepted Answer · 2019-04-13 20:08:22Z

0

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.

answered Apr 13, 2019 at 20:08

Adim Victor

1046 bronze badges

Comments

Tomáš Hübelbauer · Accepted Answer · 2019-05-28 08:23:31Z

0

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.

answered May 28, 2019 at 8:23

Tomáš Hübelbauer

11k17 gold badges76 silver badges146 bronze badges

Comments

Koder90 · Accepted Answer · 2020-05-27 14:55:29Z

0

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.

answered May 27, 2020 at 14:55

Koder90

194 bronze badges

Comments

Ace · Accepted Answer · 2020-07-10 16:27:06Z

0

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.

edited Jul 10, 2020 at 16:27

Ace

7109 silver badges39 bronze badges

answered Jul 10, 2020 at 15:15

Sourabh

133 bronze badges

Comments

Emmanuel Sahr Sewah · Accepted Answer · 2020-11-10 21:33:50Z

0

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.

answered Nov 10, 2020 at 21:33

Emmanuel Sahr Sewah

131 silver badge3 bronze badges

Comments

Sreesankar G Warrier · Accepted Answer · 2020-11-19 09:19:39Z

0

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

answered Nov 19, 2020 at 9:19

Sreesankar G Warrier

12 bronze badges

Comments

isherwood · Accepted Answer · 2022-01-04 19:33:36Z

Started getting this error in Azure DevOps yesterday out of nowhere when running npm run build:

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

However when looking at npm ci that completed it was full of errors like:

FetchError: Invalid response body while trying to fetch https://registry.npmjs.org/@babel%2fcompat-data: ENOENT: no such file or directory, lstat 'D:\a\1.npm_cacache\content-v2\sha512\58\0b\dc7dce0b33e86d97736b3c419005951e32af28dda3f5b8c746f16d53d4baed1dc2fd2493e9310f744696008400bf8c91ca84f9fb3ebf541ba93a541b144a'

When commenting out the cache everything started working again:

npm_config_cache: $(Pipeline.Workspace)/.npm

- task: Cache@2
  inputs:
    key: 'npm | "$(Agent.OS)" | $(clientApp)\package-lock.json'
    restoreKeys: |
       npm | "$(Agent.OS)"
    path: $(npm_config_cache)
  displayName: Cache npm

The weird thing is that it has worked for over a year up until yesterday (2021-12-02) and we use the exact same code for caching as Microsoft has documented.

https://learn.microsoft.com/en-us/azure/devops/pipelines/release/caching?view=azure-devops#nodejsnpm

Noting Degraded or Unhealthy on Azure DevOps Status

https://status.dev.azure.com/

Collectives™ on Stack Overflow

35 Answers 35

6 Comments

5 Comments

6 Comments

3 Comments

no need to do more!!!

1 Comment

1 Comment

2 Comments

Comments

Comments

1 Comment

React Scripts Not Recognized as internal/external script

Step by Step Solution:

Still Not Resolved?

1 Comment

This is how I fix it

To update the path variable

Comments

Comments

Comments

2 Comments

1 Comment

1 Comment

Comments

2 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Linked

Related