Repository navigation
Bug: react-scripts 4.0.1 : EBUSY: resource busy or locked, open 'C:\...\project\.eslintcache #10146
Description
Describe the bug
An error is emit after a yarn start (same with yarn build)
EBUSY: resource busy or locked, open C:\...\project\.eslintcache
Seems there is a concurential read/write on this file
Did you try recovering your dependencies?
Yes
$ npm --version
6.14.8
$ yarn --version
1.22.10
Which terms did you search for in User Guide?
- eslintcache lock
- windows lock
Environment
$ npx create-react-app --info
npx: installed 67 in 4.664s
Environment Info:
current version of create-react-app: 4.0.1
running from C:\Users\myuser\AppData\Roaming\npm-cache\_npx\15308\node_modules\create-react-app
System:
OS: Windows 10 10.0.19042
CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Binaries:
Node: 14.15.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 87.0.4280.66
Edge: Spartan (44.19041.423.0), Chromium (87.0.664.47)
Internet Explorer: 11.0.19041.1
npmPackages:
react: Not Found
react-dom: Not Found
react-scripts: Not Found
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce
- Create a project in typescript with eslint
- Seems that the problem occurs only when there are a lot of files to build
- Use react-scripts 4.0.1 (The version 4.0.0 works)
- On "yarn start", an error occurs (90% of time but not always)
Expected behavior
yarn start works :)
Actual behavior
Reproducible demo
It's the difficult part.
The issue happen only on Windows (Due to a windows file locking) and when the project contains a lot of files
So, create a minimal project is hard and I cannot give you the project of my company
Activity
ianschmitz commentedon Nov 25, 2020
You may want to file this in the
eslintrepo? We're not doing anything special on our end AFAIK other than enabling the webpack plugin.pinonpierre commentedon Nov 26, 2020
Thanks for your answer
Seems environmental because it works on some machines but not on some others. Very complex to identify.
So let's close this ticket
raFTv01d commentedon Nov 30, 2020
same problem
pinonpierre commentedon Dec 8, 2020
I reopened because it happen less often when I disable my Antivirus (Sophos) but it still have the issue sometimes
pinonpierre commentedon Dec 8, 2020
No way to reproduce the issue with "eslint --cache ."
Happen only when launched from react-script.
Is react-script launch multiple times eslint?
AndrePinto-NET commentedon Jan 27, 2021
Facing the same issue, and my colleagues the same. This happened after the upgrade to version 4.0.1
npm run start and npm run build both fail with the same error
andrew-ares commentedon Jun 10, 2021
Any updates on this? Same issue here.
pinonpierre commentedon Jun 10, 2021
No, I never solved the issue