React error from chokidar

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

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

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

. 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;

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:

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:

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).

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

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

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

. and did not run the corresponding npm install:

Follow these steps:

1. Delete the «node_modules» folder
2. Run npm install
3. Run npm cache clean

While using @Output(), remove auto imported statement

import < EventEmitter >from ‘protractor’;

and include import EventEmitter from existing

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

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

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

How to insert in package.json

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

Had this in VueJs (2) — installed a module, then uninstalled it ( npm uninstall ) and forgot to delete the «import » from the .vue file. Silly but there it was.

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

just remove it and the problem was gone!

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.

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.

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 .

And then serve again your project !

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

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.

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

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

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:

for yarn:

• 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’

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.

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.

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.

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

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

Источник

Error: No version of chokidar is available. Tried chokidar@2 and chokidar@3. after upgrading npm to 7.*.* #10811

Describe the bug

using ejected CRA , it compiles successfully and then it breaks showing below error.. it started happend when i updated npm to 7 from 6

Did you try recovering your dependencies?

i tried runnung npm npm cache verify && rm -rf node_modules/ && npm i but it did not worked

Environment

node: v14.16.0
npm: 7.9.0

OS: Linux (Ubuntu)
├── webpack-dev-server@3.11.0
├── webpack-manifest-plugin@2.2.0
├── webpack@4.44.2

Steps to reproduce

Expected behavior

should run the server succsessfully

Actual behavior

The text was updated successfully, but these errors were encountered:

OK, so this actually seems to be a Node issue, I was running 15.14 and running into this issue.

I’ve installed nvm and set it to use Node 12.22.1 (latest v12 at time of writing) and npm run start now works correctly.

This makes sense because the npm i message indicated that chokidar would not work on Node 14+.

It looks like the chokidar requirements comes from react-scripts->webpack-dev-server and unfortunately, they don’t upgrade to chokidar v3 until webpack-dev-server v4, which is still in beta. So, I guess we’re stuck with running CRA on Node 12 for now.

OK, so this actually seems to be a Node issue, I was running 15.14 and running into this issue.

I’ve installed nvm and set it to use Node 12.22.1 (latest v12 at time of writing) and npm run start now works correctly.

This makes sense because the npm i message indicated that chokidar would not work on Node 14+.

It looks like the chokidar requirements comes from react-scripts->webpack-dev-server and unfortunately, they don’t upgrade to chokidar v3 until webpack-dev-server v4, which is still in beta. So, I guess we’re stuck with running CRA on Node 12 for now.

As far as I know, you should be able to use Node v14 so there is no need to downgrade all the way to v12. Node v14 (14.16.1) is current LTS release so it might be better to use it compared to v12.

Yep, @marko-hologram — that’s what I’m saying, 14+ isn’t working, people (like OP & myself) are getting this error.

It’s possibly also a Windows (myself) vs Mac/Unix issue. I’ve been hitting a lot of weird stuff lately trying to work on a multi-OS team.

Yep, @marko-hologram — that’s what I’m saying, 14+ isn’t working, people (like OP & myself) are getting this error.

It’s possibly also a Windows (myself) vs Mac/Unix issue. I’ve been hitting a lot of weird stuff lately trying to work on a multi-OS team.

Yeah, but I’m saying that v14 should be working and you don’t need to downgrade all the way to v12. I tested on Windows only tho.

its something definitely wrong with npm 7.*.* .. i tried npm i —legacy-peer-deps and it worked for me.

however it shouldn’t be like this and dependencies should handled in latest stable version..
also haven’t tried removing node_modules and running npm i after it..

I concur with @m-nathani . The issue is definitely at least partially related to npm 7.*.* . npm version 6.14.12 (Node version 14.16.1) does not have the problem for me, whereas npm version 7.11.1 (same version of Node) definitely does. It is also specifically a Windows issue.

I concur with @m-nathani . The issue is definitely at least partially related to npm 7.*.* . npm version 6.14.12 (Node version 14.16.1) does not have the problem for me, whereas npm version 7.11.1 (same version of Node) definitely does. It is also specifically a Windows issue.

I’m using ubuntu 20.04 and npm v7.11.1 and I’m also having the same problem here.

Yeah, OK. My apologies, I thought it was node but it’s because node installs npm alongside it.

Mac running Node 15.8 and NPM 7.5.3 works fine.
Ubuntu 18 running Node 15.9 and NPM 7.5.3 works fine.
Windows running Node 15.14 and NPM 7.7.6 shows this issue.
Windows running Node 15.14 and NPM 7.5.3 works fine! 🎉

Did some more testing, 7.5.4 works, 7.5.5+ fails.

Same here. v14.16.1 with npm 7.5.4 works as well

i am using 7.9.0 and its still not fixed, not sure if this is fixed in the latest version :/

Same issue here. still no news? It’s pretty critical I think.

I can confirm that downgrading to npm@7.5.4 works.

It also started working with npm@7.13.0 after running npm update —force command. Looks like the reason is that after the command watchpack starts using v3 of chokidar:

Faced this issue when I updated from npm 6 to npm 7. I have not ejected. First I just installed chokidar as a dev dependency and then it works again with Node 14.16.0 npm 7.15.0

Edit: I just tried removing the dev dependency and then using «npm update chokidar» which updated my package-lock.json it now also works without having it as a dev dependency in the package.json

Why I have to do this: no idea.

I can confirm that downgrading to works. npm@7.5.4

It also started working with after running command. Looks like the reason is that after the command starts using v3 of chokidar: npm@7.13.0«npm update —force«watchpack

I can confirm that downgrading to works. npm@7.5.4

It also started working with after running command. Looks like the reason is that after the command starts using v3 of chokidar: npm@7.13.0«npm update —force«watchpack

Thanks, that solved my problem. @samuliasmala

Источник

Error: Cannot find module ‘fsevents’ #828

Describe the bug
When precompile assets :

Error: Cannot find module ‘fsevents’ from ‘/home/bas/app_8f0c7269-96f9-445b-a4f0-8b9ed34d7058/node_modules/chokidar/lib’

Versions (please complete the following information):

• Chokidar version : chokidar «^2.0.2»
• Node version : Install via Yarn
• OS version: Linux (sorry no more detail my server production is like an Heroku)

During Yarn Install

info «fsevents@1.2.8» is an optional dependency and failed compatibility check. Excluding it from installation.

Use
My application is a Rails App 5.2 and I use gem «browserify-rails».

Chokidar is a dependency of «watchpack».
«watchpack» is a dependency of «webpack».

Question
Why «fsevents» optionalDependency fail when compile assets?

The text was updated successfully, but these errors were encountered:

fsevents is only installed for macos. It is not installed on Linux. You should not be seeing this error «Cannot find module ‘fsevents’ from» at all. So, kinda strange.

Solution:
rm -rf node_modules package-lock.json yarn.lock
and then
npm install or
yarn install

Ensure you are using chokidar v3 and higher! Chokidar v2 uses fsevents v1, which is deprecated. Note: you will need to use node.js v8.10 or higher for chokidar v3.

You can delete your node_modules folder and yarn.lock file and run yarn install again this works for me

I am getting same error on Windows

I’m getting the same error on Manjaro with chokidar v3.4.0

I am getting the same error on Windows for chokidar version 2.0
Any update or resolution on this issue?

look in top file, can be import same this «const < ContextReplacementPlugin >= require(«webpack»);»

I’m having the same problem with Chokidar v3.5.1 on Kubuntu 20.04 LTS

I have an Electron App (writtten in VUE). that uses chokidar to watch file system events. complile just started to fail with:
ning in ./node_modules/chokidar/lib/fsevents-handler.js

Module not found: Error: Can’t resolve ‘fsevents’ in ‘C:Codesidekicknode_moduleschokidarlib’
version:
«chokidar»: «^3.5.1»,

the app actually compiles despite this error, but upon running, I get a webpack error:

Uncaught TypeError: The «original» argument must be of type Function
at promisify (util.js?3022:602)
at Object.eval (index.js?b048:9)
at eval (index.js:284)
at Object../node_modules/readdirp/index.js (chunk-vendors.js:9146)
at webpack_require (index.js:849)
at fn (index.js:151)
at Object.eval (index.js?b44e:7)
at eval (index.js:969)
at Object../node_modules/chokidar/index.js (chunk-vendors.js:1804)
at webpack_require (index.js:849)

This setup was working fine until just recently. Not really sure where to go from here.

additional info. i’m on a windows 10 machine, so fsevents shouldn’t even be called, right?

So how to fix it? I have it with version 3.5.1.

I was getting this error during JS debugging sessions; turns out I had left my «break on caught exceptions» box checked. Maybe that’s helpful to someone.

Tried above solutions still getting this error. I’m on Windows 10 too. The package for me causing this is ‘electron-reloader’
. It uses chokidar 3.5.0, tried cleaning reinstalling everything.

I was able to solve (workaround) this issue by mocking the fsevents module then creating an alias for it so webpack can resolve the require :

I explain this in detail on Stack Overflow

I’ve found a workaround inspired by @totymedli which does not break fsevents on MacOS and does not require a separate file.

If you’re using Webpack, simply add the following to your webpack.config.js file.

That is indeed a better solution however I would write it like this:

I was getting this error during JS debugging sessions; turns out I had left my «break on caught exceptions» box checked. Maybe that’s helpful to someone.

This solved my problem, I was using VSCode and i dont know somehow, my checkbox for «Caught Exception» was marked.
Unchecking it resovled the problem while debugging-session in nodejs App.

I was getting this error during JS debugging sessions; turns out I had left my «break on caught exceptions» box checked. Maybe that’s helpful to someone.

This solved my problem, I was using VSCode and i dont know somehow, my checkbox for «Caught Exception» was marked. Unchecking it resovled the problem while debugging-session in nodejs App.

Thanks @hassanrazase
I had the same problem here, I was trying to solve this for 2 days already, you saved my day

Module not found: Error: Can’t resolve ‘fsevents’ in ‘/node_modules/chokidar/lib’
package.json -version:
«chokidar»: «^3.5.3»,

Uncaught TypeError: The «original» argument must be of type Function

I have an Electron App (writtten in VUE). that uses chokidar to watch file system events. complile just started to fail with: ning in ./node_modules/chokidar/lib/fsevents-handler.js

Module not found: Error: Can’t resolve ‘fsevents’ in ‘C:Codesidekicknode_moduleschokidarlib’ version: «chokidar»: «^3.5.1»,

the app actually compiles despite this error, but upon running, I get a webpack error:

Uncaught TypeError: The «original» argument must be of type Function at promisify (util.js?3022:602) at Object.eval (index.js?b048:9) at eval (index.js:284) at Object../node_modules/readdirp/index.js (chunk-vendors.js:9146) at webpack_require (index.js:849) at fn (index.js:151) at Object.eval (index.js?b44e:7) at eval (index.js:969) at Object../node_modules/chokidar/index.js (chunk-vendors.js:1804) at webpack_require (index.js:849)

This setup was working fine until just recently. Not really sure where to go from here.

additional info. i’m on a windows 10 machine, so fsevents shouldn’t even be called, right?

I`m in Linux Centos7, and I have exactly the same error? Please help

Источник