Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp

Question

Using Angular and during ng serve, I'm getting the error:

Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'
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'

I had something similar and it was because someone had added an npm package and I hadn't `npm install` after pulling their changes. — stubbzarelli, Jul 29 '20 at 12:27
Why is npm/chokidar/whatever trying to do anything with my swapfile anyways? That's... rather alarming. — Paul, Aug 26 '20 at 19:55
@stubbzarelli +1 your comment helped me to solve this issue. Thanks. — velsorange, Oct 01 '20 at 07:20
@Paul is right, this is a very red flag even if it's an honest bug — Pieter De Bie, Nov 12 '20 at 08:03
@paul "rather alarming" -- yep, warrants disciplinary action. — bvj, Dec 23 '20 at 04:31
@Paul Could you explain why this is so alarming? Chokidar uses the filesystem module from Node.js, which in turn talks to the OS. Could it be that it's just the operating system managing virtual memory allocation that sends this error back to Node? — Melvin Koopmans, Jan 14 '21 at 09:16
@MelvinKoopmans `chokidar` is a file-watcher and there's no good reason for anything to be watching root-directory files, let alone system files like those. All the answers blaming VS Code have it wrong, something appears to be screwy with `chokidar` if you ask me. (I get this running things like `webpack serve` from the command line, no editors involved -- but as many answers state, it seems to be a side-effect of other errors.) — McGuireV10, Jan 15 '21 at 09:51
@MelvinKoopmans What McGuireV10 said. I don't know if this is just the OS throwing a red herring error or not, but I would really like confirmation that npm packages are not poking around in the file system outside of their project root. — Paul, Jan 15 '21 at 15:58
I've added an answer below but it appears to be an issue with passing a path to a directory that doesn't exist to chokidar. In my case it was incorrectly passing '/public'. I suspect that as it couldn't find C:/public it was doing a watch on C:/ hence all the lock errors on files that it can't access that sit in the root of the C:/ — theirongiant, Dec 19 '22 at 20:02

score 71 · Accepted Answer · answered May 21 '20 at 13:52

71

I get this whenever I'm using VSCode and I add something similar to a component:

@Output() somename = new EventEmitter();

...and I let VSCode auto-import the supporting module. Instead of adding EventEmitter to the existing @angular/core, VSCode adds a new import to protractor which causes the error.

If you are getting this error and can't remember where the last changes were made, try searching for from 'protractor' in your code;

answered May 21 '20 at 13:52

Post Impatica

14,999
9
67
78

2

You just save me! – Jorgeblom Jun 02 '20 at 15:21
4

To caveat on this post; I ran into Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'something.sys' and it was because I allowed VSCode to import a package for me. So if you allowed VSCode to import something for you, go back and check your imports. All of them. -- Thanks! – Jason Jun 13 '20 at 14:49
1

Thanks! In my case there was a HTML style comment were left behind after HTML was updated to pug. – Zugor Nov 20 '20 at 01:56
1

love you 3000 , i have been downloading node_module multiple time – Atul Sharma Dec 24 '20 at 13:10
This is so stupid! I got this same error on IntellIj. Watch those auto-imports and stay safe. – wheeleruniverse May 28 '21 at 18:40
So does Intellij too (－‸ლ) – gleitonfranco Dec 10 '21 at 15:44
1

where exactly to add this? which directory? – makoz Nov 08 '22 at 23:08
someone please answer @makoz coz that is my question too! – Biax20 Mar 09 '23 at 00:58

Reg Edit · Answer 2 · 2020-10-19T20:27:47.760

This can happen after several different build errors. For some reason the build summary fails to report the original error and reports this instead.

(Incidentally I see the OP was using Angular and ng serve; I'm getting this in React using npm start. So I'm guessing it could happen in VS Code using any toolchain.)

I was getting this output in the VS Code terminal:

i ｢wdm｣: Failed to compile.
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'

After looking for answers on this page and elsewhere, I found nothing that worked for me.

But when I scrolled back in the VS Code terminal, I found this build error:

ERROR in ./Components/ServiceBooking/ServiceBooking/ServiceBooking.tsx
Module not found: Error: Can't resolve 'components/Common/BookingComponents/BookingTypeSelector/BookingTypeSelector' in [...]

That was a casing error in an import auto-added by VS Code. I don't know why but VS Code does that sometimes. Maybe there is something we can tweak in this project to help VS Code not to do that. Anyway, it was an error, and once I fixed it by changing "components" to "Components" in the import, the secondary errors about hiberfil.sys, pagefile.sys and swapfile.sys went away.

The moral of the tale: beware of the build summary masking build errors. Any time you hit a weird build error, first scroll back through the detailed build output to make sure you are chasing the right error (the original error, rather than a secondary error like this one).

After scrolling back like a thousand lines I found this error, thank you! — Baltasar Solanilla, May 05 '21 at 23:18

score 21 · Answer 3 · answered Sep 14 '20 at 09:21

21

check for the missing dependencies in package.json

I am using vue js I was trying to run a project and I had this error this problem was because the other developer used a global dependencies and it was not included in my node_modules folder

answered Sep 14 '20 at 09:21

Nashaat Mohamed

341
2
6

1

I had this same error at a React project and missing dependency from `package.json` was the reason. – Enes Kirimi Dec 17 '20 at 10:07
1

What about if this happens right after creating a new vue js project and installing 2 dependencies and 2 plugins via the vue ui? It is completly local and still throws this error right after fresh setup and installation of sass-loader, node-sass, vuex and vue-router. I cant seem to find an answer. – BrOsCoRe Feb 19 '21 at 14:52
1

confirming, npm install solved my problem with angular 11 app. – Janatbek Orozaly Jun 07 '21 at 22:12

score 21 · Answer 4 · edited May 20 '21 at 13:08

21

Just write npm install , it is a file viewer that warns that a dependency is not properly updated. Without reading the hidden comment among the thousands I would never have known

Solution:

npm install

edited May 20 '21 at 13:08

nart

1,508
2
11
24

answered Mar 06 '21 at 05:55

Ezequiel Miceli

221
2
2

This re-iterates an answer that is already present. – Markus Deibel Mar 06 '21 at 13:00
1

This worked for me, the higher-ranked answers were addressing specific modules that I wasn't using. – johnbr Jun 25 '21 at 12:31

score 14 · Answer 5 · edited Oct 29 '21 at 17:50

14

Follow these steps:

Delete the "node_modules" folder
Run npm install
Run npm cache clean

edited Oct 29 '21 at 17:50

D M

5,769
4
12
27

answered Apr 15 '21 at 05:52

Kuristoph Richardson

141
1
6

4

This is probably the most robust way to get rid of the problem – johnbr Jun 25 '21 at 12:31

score 6 · Answer 6 · answered May 29 '20 at 13:56

6

If you are using polyfills, this error will occur if you activated the following polyfill (from src/polyfills.ts):

/** IE10 and IE11 requires the following for NgClass support on SVG elements */
import 'classlist.js';  // Run `npm install --save classlist.js`.

...and did not run the corresponding npm install:

npm install --save classlist.js

answered May 29 '20 at 13:56

Martin Åhlin

2,730
1
20
27

Also if you updated core-js from v2 to v3 and still have imports in the v2 format in your polyfills file. – rooby Feb 18 '21 at 06:56

score 4 · Answer 7 · edited Oct 18 '20 at 14:57

4

Had this in VueJs (2) - installed a module, then uninstalled it (npm uninstall <module_name>) and forgot to delete the "import <module_name>" from the .vue file. Silly but there it was.

edited Oct 18 '20 at 14:57

Thingamabobs

7,274
5
21
54

answered Oct 18 '20 at 01:05

Greg Burman

41
1

Exactly the same situation with React for me. – zehawk Apr 20 '22 at 21:26

score 3 · Answer 8 · edited Jun 23 '20 at 04:35

3

While using @Output(), remove auto imported statement

import { EventEmitter } from 'protractor';

and include import EventEmitter from existing

import { Component, OnInit,EventEmitter } from '@angular/core';

edited Jun 23 '20 at 04:35

Menuka Ishan

5,164
3
50
66

answered Jun 04 '20 at 17:36

Antony

39
3

score 2 · Answer 9 · edited Jul 14 '20 at 08:44

2

EventEmitter() by default imported by protractor in VS code,

import { EventEmitter } from 'protractor'; remove this and import from core.

import { EventEmitter } from '@angular/core';

this solves the other issue as well which is expecting 0 arguments and have 1.

edited Jul 14 '20 at 08:44

Boken

4,825
10
32
42

answered Jul 14 '20 at 08:21

Shivaram Tolanur

59
2

score 2 · Answer 10 · answered Oct 15 '20 at 04:50

I had the same issue and I fixed via setting in package.json

"browser": {
  "http": false
}

How to insert in package.json

{
  "name": "App Name",
  "version": "0.0.0",
  "scripts": {
     // --------
  },
  "dependencies": {
     // --------
  },
  "devDependencies": {
     // --------
  },
  "browser": {
    "http": false
  }
}

If someone knows its reason that why is it necessary and what happens by adding this then please add some description to make reading more sensible. Thanks

My code worked fine for months, then I ran into this same issue and this fixed it. — Ryan Rife, Dec 04 '20 at 23:18

score 2 · Answer 11 · answered Nov 08 '21 at 09:32

2

I got this error while install Material UI designs in my react project, and after installing npm package i have no issues now.

Add:

npm i

Thanks!

answered Nov 08 '21 at 09:32

Gopalakrishnan T

453
1
4
14

score 1 · Answer 12 · answered Dec 03 '20 at 10:25

1

I had the same error because phpStorm/WebStorm added this import

import {forEach} from 'ag-grid-community/dist/lib/utils/array';

just remove it and the problem was gone!

answered Dec 03 '20 at 10:25

Christophe Le Besnerais

3,895
3
24
44

score 1 · Answer 13 · answered Jan 11 '21 at 15:08

1

I had the same issue. My colleague had installed this dependency and I simply restored packages (right click on package.json - Restore Packages) in packages.json and it seemed to fix it.

answered Jan 11 '21 at 15:08

Robgit28

268
4
18

score 1 · Answer 14 · edited Feb 21 '21 at 11:50

I got similar issue when building an ionic application. I had some similar pages and components from other application reused in this one. Once running, I receveived the message[ng] Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\pagefile.sys. This was solved by installing a missing library. The error was presented on vscode terminal, a little bit above the message presented on the screen. I felt silly because the error was there since the beginning and I haven´t realized I should have search for it.

score 1 · Answer 15 · answered Apr 27 '21 at 09:52

1

Yes, I also had a same error..

SOLUTION

It means there's some packages are not installed in your node_module. so just run this command.

npm install

And then serve again your project !

answered Apr 27 '21 at 09:52

Rohit Tagadiya

3,373
1
25
25

score 1 · Answer 16 · answered May 24 '21 at 09:07

In my case, I was facing the same issue. What I guess is, this arises due to circular dependency. I used a service that was injected in multiple components and I was retrieving all that components simultaneously. It was throwing error resource busy.... I resolved it by providing service in root instead of multiple lazy loaded modules. May be helpful for someone

score 1 · Answer 17 · answered Jun 22 '21 at 15:40

I had the same issue today and am using VueJS 3 and VS Code. Somehow my @vue/cli-service was downgraded from 4.5.0 to 3.5.3. No idea how that happened. Anyway, by updating package.json with the following and running npm install after that, it was solved.

"@vue/cli-service": "^4.5.13"

score 1 · Answer 18 · answered Dec 28 '21 at 11:06

1

In my case, the problem was randomly added import by VS CODE auto-complete. So search for the dependency and remove if it is not in use.

answered Dec 28 '21 at 11:06

omer faruk kalkan

75
1
11

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](/help/how-to-answer). – Community Dec 28 '21 at 12:36

theirongiant · Answer 19 · 2022-12-20T10:20:19.307

The root cause of this is a directory that does not exist being passed to chokidar. Run 'node ls chokidar' to get a list of packages you are using that use chokidar, then double check any paths you are setting in any config files that might be being used by these packages. In my case it was due to me setting the static option for webpack-dev-server to '/public' rather than path.join(__dirname, 'public') in my webpack config.

edit After looking into it further if you pass a path that doesn't exist to chokidar it will look down the path and start watching the first directory it finds that exists. In the case where that is C:/ then these EBUSY errors will occur against system protected files found there.

score 0 · Answer 20 · answered Dec 23 '20 at 10:48

0

I needed to re-install the npm packages that were showing later in the error logs (in my case bootstrap and react-router-dom)

answered Dec 23 '20 at 10:48

Patricia

2,885
2
26
32

score 0 · Answer 21 · answered Apr 24 '21 at 14:09

0

For Vue.js, Check if you have import like this import Vue from "*.vue"; change it to import Vue from "vue"; It was auto imported by VsCode

answered Apr 24 '21 at 14:09

Pranoy Sarkar

1,965
14
31

score 0 · Answer 22 · answered Apr 29 '21 at 12:20

This bug is related to Babel and it's preset, I know the screenshot is related to NuxtJS but this npm command solves the problem for Angular as well, since they are using almost the same configuration.

for npm:

npm i -S core-js@2.5.7

for yarn:

yarn add core-js@2.5.7

core-js/core/dict in ./node_modules/babel-loader/lib??ref--2-0!./node_modules/vue-loader/lib??vue-loader-options!./pages/index.vue?vue&type=script&lang=js&

To install it, you can run: npm install --save core-js/core/dict

WARN Error from chokidar (C:): Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'

score 0 · Answer 23 · edited Apr 30 '21 at 23:29

I got this error while using angular multi-project setup. I was using firebase functions in my project. The cause of my issue was having a source file located under "projects/my-project/src/app/*" import another file located under "projects/my-project/functions/src*". The functions folder was a sub project folder and had it's own "node_modules" folder.

SOLUTION

So I searched for all import references under "projects/my-project/functions/src*" containing "/functions/". I was using Web Storm but most modern IDE's and text editors like vscode have this capability.

score 0 · Answer 24 · answered Jun 30 '21 at 13:54

I had the same issue, and my resolution was to change absolute path when including components (added automatically by VS Code), to relative path, and issue gone.

Changed from:

import { FirebaseCrudService } from 'app/src/firebase/crud/firebase-crud.service';

to:

import { FirebaseCrudService } from '../../firebase/crud/firebase-crud.service';

and it worked.

score 0 · Answer 25 · answered Aug 05 '21 at 09:28

0

In my case this errors were totally unrelated to chokidar. The build has failed because someone did a commit with errors and before even trying to compile i ran "ng serve" I couldn't see the errors.

Either scroll up to see the errors or make a "ng build" before serving so you can see what to fix.

answered Aug 05 '21 at 09:28

Ruben Miquelino

977
9
13

to be on safe side you can use `ng build --prod` in `pre-push` hook in package.json as `"husky": {"hooks":{"pre-push": "ng build --prod"}},` – Analyst Sep 02 '21 at 05:22

score 0 · Answer 26 · answered Sep 03 '21 at 13:06

The solution for me: There's a problem with 2 developers installing dependencies in project using npm and yarn. I use yarn, so:

rm package-lock.json //deleting the package-lock.json  
rm -rf node_modules //deleting the node_modules
yarn //installing the dependencies with yarn
yarn cache clean //cleaning the cache
yarn serve //run the project

score 0 · Answer 27 · answered Mar 03 '22 at 20:26

In Linux this type of errors happen when chokidar doesn't get enought file watchers from the system. Thus, increasing then in the system (or reduce the number of files whatched on the project) solves the problem.

The question here is how to do this on Windows.

score 0 · Answer 28 · answered Mar 25 '22 at 18:41

I had a similar problem with my cypress runner. I was getting the following error:

Error from chokidar (C:): Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp'

What happened was that VS automatically put a line on top of my code that read:

const { each } = require("cypress/types/bluebird")

I just removed it from my code and it worked fine. Hope that will help a lot of y'all!

score 0 · Answer 29 · answered Apr 12 '22 at 09:58

Vue/Nuxt.js

I got this same error in vue/nuxt js application, it happened because of mix package manager that leads to unsynchronized lock files, it is advised not to mix package manager in order to avoid resolution inconsistencies caused by unsynchronized lock files.

Solution: Delete node_modules folder and use npm/yarn depending upon what you used to generate lock file

score 0 · Answer 30 · answered May 22 '22 at 11:17

0

It happened to me when I imported the MatSlideToggle class from:

import {MatSlideToggle} from '@angular/material/slide-toggle/slide-toggle';

instead of import it from:

import {MatSlideToggle} from '@angular/material/slide-toggle';

I changed it and now everything works well.

answered May 22 '22 at 11:17

Avraham Weinstein

582
4
13

This does not really answer the question. If you have a different question, you can ask it by clicking [Ask Question](https://stackoverflow.com/questions/ask). To get notified when this question gets new answers, you can [follow this question](https://meta.stackexchange.com/q/345661). Once you have enough [reputation](https://stackoverflow.com/help/whats-reputation), you can also [add a bounty](https://stackoverflow.com/help/privileges/set-bounties) to draw more attention to this question. - [From Review](/review/late-answers/31834946) – Sumit Sharma May 27 '22 at 12:17

Deltas Lephalala · Answer 31 · 2023-02-28T20:32:57.433

0

As simple as this might seem - I fixed this issue by reverting/discarding the changes I had in my solution - Alternatively you can save your changes into a notepad if you have a lot of changes that you might not want to lose (you can alway put your chnages back). As the result, 'ng build' ran without any problems.

edited Feb 28 '23 at 20:32

answered Jul 16 '22 at 13:37

Deltas Lephalala

1
2

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jul 20 '22 at 20:11

score 0 · Answer 32 · answered Nov 16 '22 at 12:52

0

For Vue, here are the steps to follow:

Run npm install
npm run serve

Notes: npm install will audit packages and add necessary packages if needed. Hope it will help.

answered Nov 16 '22 at 12:52

Robiul Hossain Shah

369
4
9

score 0 · Answer 33 · answered Feb 28 '23 at 09:20

0

The issue can be related to cache. Here is what works

Delete node_modules directory

Delete package-lock.json

Run npm install

Now it should work!

answered Feb 28 '23 at 09:20

Zafrullah Syed

1,170
2
15
38

score 0 · Answer 34 · answered Mar 01 '23 at 08:22

By mistake I import Router module from 'express' like this:

import { Router } from 'express';

It should be import from '@angular/router' like this:

import { Router } from '@angular/router';

For you there could be different module which not correctly imported, so you can check lastly added some module's path.

Error from chokidar (C:\): Error: EBUSY: resource busy or locked, lstat 'C:\DumpStack.log.tmp

34 Answers34

Linked