react-scripts: command not found

Question

I am currently trying to use create-react-app which uses three different packages: react, react-scripts and react-dom. I have installed create-react-app and then when I change into the directory and hit npm start I get a react-scripts: command not found. I've ran into a lot of problems with this. I can see react-scripts is in my node_modules folder but I keep getting command not found when trying to run npm start. I tried to delete and re-install all of my node_modules but it didn't work. Anyone else having this issue?

 ✘ ✝  Node/toDoApp/my-test   master±  npm start

> [email protected] start /Users/jzilch/Desktop/Web 
Projects/Node:Express/Node/toDoApp/my-test
> react-scripts start

sh: react-scripts: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] start: `react-scripts start`
npm ERR! spawn ENOENT
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.

Tried this with Yarn too and got the following after first trying to add with Yarn Globally ✝  Node/toDoApp/my-test   master±  yarn start yarn run v1.3.2 $ react-scripts start /bin/sh: react-scripts: command not found error Command failed with exit code 127. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. — James Zilch
– James Zilch, Commented Dec 2, 2017 at 21:18
If you run npm install in the project directory. What happens? — Joshua Underwood
– Joshua Underwood, Commented Dec 2, 2017 at 21:19
Everything installs but I do get an error on fsevents ` > [email protected] install /Users/jzilch/Desktop/Web Projects/Node:Express/Node/toDoApp/my-test/node_modules/fsevents > node install events.js:182 throw er; // Unhandled 'error' event ^ ` — James Zilch
– James Zilch, Commented Dec 2, 2017 at 21:22
Thanks. I tried to uninstall and re-install Node with Homebrew but still is not working. With yarn I do get more incite on what might be breaking. Yarn start return /bin/sh: react-scripts: command not found Leading me to believe that its trying to find this fine in /bin/sh: instead of node_modules. Not sure on this one as system files are not my forte — James Zilch
– James Zilch, Commented Dec 2, 2017 at 22:43

user5395907 · Accepted Answer · 2018-01-02 16:59:31Z

111

Firstly Delete package-lock.json file in your project folder.

And then install dependencies again by npm install. That should solve this issue.

answered Jan 2, 2018 at 16:59

user5395907

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

6 Comments

Mohan Krishna Sai Over a year ago

While deleting use "rm -rf"

Jim Over a year ago

package.json is not a directory so -rf should not really be necessary here.

Drew Delano Over a year ago

package-lock.json is the file they're suggesting you delete, not package.json -- @Jim assuming this was just a typo, but want to save people some time if possible.

Siavoshkc Over a year ago

Why suggesting package-lock.json should be deleted?

David Maness Over a year ago

@Siavoshkc package-lock.json ensures specific versions are installed when installing node modules. I assume the intention behind deleting it is to allow installation of a later version of whatever library may be causing this issue.

|

NotQuiteApex · Accepted Answer · 2023-03-02 11:47:55Z

47

Delete the /node_modules directory and the package-lock.json file using the rm command:

rm -rf node_modules
rm -rf package-lock.json

Install react-scripts using the following command:

npm install react-scripts

Install the dependencies using the following command:

npm install

Start the local server by running the following command:

npm run start

edited Mar 2, 2023 at 11:47

NotQuiteApex

34 bronze badges

answered Feb 3, 2019 at 17:17

venky royal

2,3042 gold badges15 silver badges22 bronze badges

2 Comments

Luca Perico Over a year ago

You are deleting package.json not package-lock.json with your command :)

General Grievance Over a year ago

In case the edit doesn't go through, the last note is questionable. If you have to resort to sudo for npm commands, there's likely something wrong with the node installation.

Rocío García Luque · Accepted Answer · 2024-02-14 08:47:53Z

32

This usually happens because of a bad npm packages installation (using npm and yarn at the same time?). It can be dispiriting, but if you try these steps, it should work.

NPM solution:

At the project's root folder, run:

> rm -rf node_modules
> rm -rf package-lock.json
> npm install

YARN solution:

At the project's root folder, run:

> rm -rf node_modules
> rm -rf yarn.lock
> yarn upgrade
> yarn

Next time you want to add a dependency using create-react-app, I recommend you to use 'yarn add' instead of 'npm install'. (Source: https://github.com/facebook/create-react-app/issues/1155)

edited Feb 14, 2024 at 8:47

answered Mar 8, 2018 at 11:06

Rocío García Luque

3,86735 silver badges32 bronze badges

Comments

swdev · Accepted Answer · 2019-07-26 08:11:35Z

11

I use this in a dockerizer enviroment. I already install locally in node_modules using package.json.

so, I added this:

RUN npm install -g react-scripts
RUN npm install

That solved my confusing issue

answered Jul 26, 2019 at 8:11

swdev

5,2578 gold badges68 silver badges112 bronze badges

Comments

Dirk Diggler · Accepted Answer · 2020-12-14 02:07:31Z

9

One option is to install the react-scripts package globally using the -g flag. This will make the command available to node, regardless of the working directory.

This command will install react-scripts globally:

npm install -g react-scripts

edited Dec 14, 2020 at 2:07

Dirk Diggler

8651 gold badge11 silver badges24 bronze badges

answered Nov 13, 2020 at 2:17

Jamil Matheny

1601 silver badge8 bronze badges

Comments

ignacio · Accepted Answer · 2020-05-13 10:28:35Z

7

As I was using yarn, I had to run yarn add react-scripts.

answered May 13, 2020 at 10:28

ignacio

1,1972 gold badges16 silver badges29 bronze badges

Comments

MouseAndKeyboard · Accepted Answer · 2019-12-08 12:39:37Z

6

I had this problem for ages and I eventually found my solution by sheer chance.
Turns out, you can't have spaces in any folder names.

e.g. ~/projects/tutorial/ReactJS/JavaScript Framework: ReactJS/app-name won't work because JavaScript Framework: ReactJS contains spaces.
In general, it's probably not great practice to be using spaces in folder/file names anyway but I hope this saves someone at least 4 hours of trial and error.

I would recommend removing the : from your folder names too! (just to be safe)

answered Dec 8, 2019 at 12:39

MouseAndKeyboard

4555 silver badges8 bronze badges

2 Comments

JJ Gerrish Over a year ago

My issue was caused by me using npx create-react-app app-name inside of a folder named "npm/node" or npm:node. Using the command in a different directory named npm-node worked.

Daniyal Malik Over a year ago

In addition to this answer, an ampersand (&) can also cause this issue. This happened in my case.

Ved Prakash · Accepted Answer · 2019-11-13 12:20:30Z

1

I fixed it by changing folder name in my local system, from

new/landing

to

new_landing

However, the git branch name remains like "new/landing". This was the case with my MAC system.

answered Nov 13, 2019 at 12:20

Ved Prakash

1217 bronze badges

Comments

Oussama Jabrane · Accepted Answer · 2022-08-10 11:53:31Z

1

For me, I deleted the project and initialized another one with the npm create-react-app <Folder Name> script. Instead of create-react-app <Folder Name>. It worked for me.

answered Aug 10, 2022 at 11:53

Oussama Jabrane

113 bronze badges

Comments

General Grievance · Accepted Answer · 2023-03-02 15:13:47Z

1

Delete your

node_modules
yarn.lock
manifest_lock.json

edited Mar 2, 2023 at 15:13

General Grievance

5,12039 gold badges39 silver badges60 bronze badges

answered Jan 29, 2018 at 16:49

user8219568

Comments

Meghana Penmetsa · Accepted Answer · 2023-04-13 12:00:53Z

0

$yarn $yarn run start

Running these commands two commands worked for me.

answered Apr 13, 2023 at 12:00

Meghana Penmetsa

1

1 Comment

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

KKM · Accepted Answer · 2023-05-13 12:19:40Z

0

If anyone's having this issue with yarn, you can do

yarn global add react-scripts

and then delete your package-lock.json and node_modules folder.

Then, you can navigate to the main folder, and just do yarn and it will do a fresh install of your package.json dependencies.

answered May 13, 2023 at 12:19

KKM

7747 silver badges13 bronze badges

Comments

Mike Q · Accepted Answer · 2025-07-25 02:27:48Z

0

FWIW,

I had gone through re-installing everything, btw, you shouldn't use the -g option (I believe) because it installs globally and it can cause issues for React (at least for me). anyway after trying everything above it had to do with the react-scripts line in my package.json file.

Fix Update `package.json`

Edit your package.json and change this line:

"react-scripts": "^0.0.0"

to a particular version,

"react-scripts": "5.0.1"

Not entirely sure why because I would think the original value would install any available version.

answered Jul 25 at 2:27

Mike Q

7,4855 gold badges62 silver badges69 bronze badges

Collectives™ on Stack Overflow

react-scripts: command not found

13 Answers 13

6 Comments

2 Comments

Comments

Comments

Comments

Comments

2 Comments

Comments

Comments

Comments

1 Comment

Comments

Fix Update `package.json`

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

13 Answers 13

6 Comments

2 Comments

Comments

Comments

Comments

Comments

2 Comments

Comments

Comments

Comments

1 Comment

Comments

Fix Update package.json

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related

Fix Update `package.json`