Bug: react-scripts 4.0.1 : EBUSY: resource busy or locked, open 'C:\...\project\.eslintcache

[pinonpierre]

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

1. Create a project in typescript with eslint
2. Seems that the problem occurs only when there are a lot of files to build
3. Use react-scripts 4.0.1 (The version 4.0.0 works)
4. 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

[ianschmitz]

You may want to file this in the eslint repo? We're not doing anything special on our end AFAIK other than enabling the webpack plugin.

[pinonpierre]

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]

same problem

[pinonpierre]

I reopened because it happen less often when I disable my Antivirus (Sophos) but it still have the issue sometimes

[pinonpierre]

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]

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]

Any updates on this? Same issue here.

[pinonpierre]

No, I never solved the issue