Why I am getting this error message when I run react js project first time in my system?

Question

When I run npm start, I get this error message:

Error from chokidar (C:): Error: EBUSY: resource busy or locked, lstat 'C:\hiberfil.sys' Error from chokidar (C:): Error: EBUSY: resource busy or locked, lstat 'C:\pagefile.sys' Error from chokidar (C:): Error: EBUSY: resource busy or locked, lstat 'C:\swapfile.sys' Error from chokidar (C:\node_modules): Error: EBUSY: resource busy or locked, lstat 'C:\hiberfil.sys' Error from chokidar (C:\node_modules): Error: EBUSY: resource busy or locked, lstat 'C:\pagefile.sys' Error from chokidar (C:\node_modules): Error: EBUSY: resource busy or locked, lstat 'C:\swapfile.sys' Error from chokidar (C:\node_modules): Error: EBUSY: resource busy or locked, lstat 'C:\hiberfil.sys' Error from chokidar (C:\node_modules): Error: EBUSY: resource busy or locked, lstat 'C:\pagefile.sys' Error from chokidar (C:\node_modules): Error: EBUSY: resource busy or locked, lstat 'C:\swapfile.sys'

\AppData\Local\Temp\ did you try removing everything in the `npm` folder? — ABGR, May 24 '20 at 11:43

score 18 · Answer 1 · answered Jun 29 '20 at 15:40

18

follow the below steps:

Delete node_modules folder.
run npm install .
run npm cache clean .

*first 2 steps worked for me.

answered Jun 29 '20 at 15:40

kartik tyagi

6,256
2
14
31

3

Thanks. The first two steps worked for me as well. – Tan Mar 10 '21 at 23:24
However, it started throwing same error again after I imported newly installed component in my code. And it is not going away even though I performed step 1 and 2 again. – Tan Mar 11 '21 at 23:53
The reason for the error thrown would majorly be caused by the use of an outdated versions of packages (dependencies). So, the best shot would be to follow the above 3 steps or upgrade every single dependency in the project (check inside package.json) – kartik tyagi May 10 '21 at 07:14
2

Yeah, I was missing some dependencies in package.json and it started working fine. Do you know why `npm cache clean` thorws this error `npm ERR! As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use 'npm cache verify' instead.` – Tan May 10 '21 at 22:13
There could be many reasons for that. It may occur due to npm didn't download properly, permission problem (try executing cmd with `sudo`), or It could be (most obiviously) due to not clearing cache properly (use `npm cache clean --force`) in that case. Also, the npm>5 have some upgrades, if you'll try removing and installing npm again, then this error may not occur. – kartik tyagi May 11 '21 at 23:58
Yeah, I had to use `npm cache clean --force` but whenever I checked the status using `npm verify` (I hope I wrote the command correctly), it always showed some 0MB bytes, even before running `npm cache clean --force`. I wonder if any cache is getting cleared or not. – Tan May 12 '21 at 03:39

score 3 · Answer 2 · edited Mar 11 '21 at 16:36

3

Delete node_modules folder and then run:

npm install && npm clean-install react-scripts

edited Mar 11 '21 at 16:36

Shayan Shafiq

1,447
5
18
25

answered Jul 16 '20 at 13:42

Dohd

359
3
7

score 2 · Answer 3 · edited Mar 11 '21 at 14:47

2

I fixed this issue by installing the chart.js: 2.5.0 dependency. The issue with my code is that I was using react-chartjs-2 dependency and in order to use it, I needed to install chart.js.

Note that I had to install it manually. npm i wasn't working. Hope it helps.

edited Mar 11 '21 at 14:47

Shayan Shafiq

1,447
5
18
25

answered Jun 05 '20 at 12:17

Odair Vaz

41
1
6

score 2 · Answer 4 · answered Aug 31 '20 at 06:07

2

running

npm install --cache /tmp/empty-cache

Solves the problem for me.

answered Aug 31 '20 at 06:07

Lokeshwaran

21
4

score 2 · Answer 5 · edited Mar 12 '21 at 08:11

2

I faced the same problem. Then I was importing a package that I didn't yet install. So make sure you have installed all the packages that you are using in the import statements at the top of your React component.

edited Mar 12 '21 at 08:11

Shayan Shafiq

1,447
5
18
25

answered Nov 20 '20 at 11:00

hadeel salah

21
3

fair, I understand that, but wouldnt the error be higher up at all to where we could get more of a "cannot find module `x` in `index.js` etc"? Makes things hard to catch from an error perspective – Coty Embry Dec 18 '20 at 22:24

score 1 · Answer 6 · answered Sep 10 '20 at 15:36

1

deleting node_modules folder and then running:

npm install
npm cache clean

worked for me!

answered Sep 10 '20 at 15:36

score 1 · Answer 7 · edited Mar 12 '21 at 09:51

1

I had the same problem with nativscript/angular router.

Problem was bad import. I mean deep import like @nativescript/angular/router.

I changed it to @nativescript/angular because there is no more deep imports.

Maybe it is a similar problem with your react-router.

edited Mar 12 '21 at 09:51

Shayan Shafiq

1,447
5
18
25

answered Sep 12 '20 at 15:19

quince

165
1
11

score 1 · Answer 8 · edited Mar 11 '21 at 15:51

1

I had the same issue. You're probably working in a Linux environment. If it is so, before running the start script, you need to switch the terminal to sudo user.

This approach fixed my issue.

edited Mar 11 '21 at 15:51

Shayan Shafiq

1,447
5
18
25

answered Feb 21 '21 at 12:31

DH Fernando

21
2

score 0 · Answer 9 · edited Mar 13 '21 at 08:39

0

Here are some things you can try to fix the error message:

Delete all directories on C:\Users\<Username>\AppData\Local\Temp\ that start with npm-.
npm cache clean
Run as an administrator

Ref: npm Error : EBUSY resource busy or locked / npm | GitHub

edited Mar 13 '21 at 08:39

karel

5,489
46
45
50

answered May 24 '20 at 11:48

ABGR

4,631
4
27
49

1

The problem was got solved by running the same command with "Run as Administrator" in command prompt. – Vikram Shekhawat May 24 '20 at 12:52

score 0 · Answer 10 · answered Jun 01 '20 at 09:12

0

Deleted all my node modules and reinstalled, worked for me

answered Jun 01 '20 at 09:12

Davison Vurayayi

1

score 0 · Answer 11 · answered Sep 07 '20 at 12:17

0

On Arch Linux just run:

rmdir -rf node_modules
sudo pacman -S npm
npm install -g semver
sudo pacman -Sy node-gyp

answered Sep 07 '20 at 12:17

Lamech Desai

709
6
11

score 0 · Answer 12 · edited Mar 13 '21 at 13:51

0

Delete all node_modules and check npmrc file whether it's there in C:\Users<username> folder or not. If not, then create it and again do npm install followed by npm cache clean and npm run start.

edited Mar 13 '21 at 13:51

Shayan Shafiq

1,447
5
18
25

answered Sep 25 '20 at 11:15

shivam singh rajawat

1

score 0 · Answer 13 · edited Nov 02 '20 at 19:56

0

I am using Yarn rather than npm

Delete the node_modules folder
yarn add
npm cache verify

edited Nov 02 '20 at 19:56

Paul Roub

36,322
27
84
93

answered Nov 02 '20 at 19:40

azeem

341
3
4

Why I am getting this error message when I run react js project first time in my system?

13 Answers13

Linked