.eslintcache constantly generated

[dominikabieder]

Is there a way of disabling .eslintcache generation? I'm struggling to find the answer in the documentation.

[Adam-Ross]

Same... This just started happening to me today.

[Safnaj]

Same for me as well. Couldn't find the answer anywhere else.

[nrayburn-tech]

It's part of v4, I think. There's a PR to have it moved into the node_modules folder, which I believe is consistent with some other caches.

It's there to help speed up the linting during both development runs and production builds. It can mostly be ignored, but I don't think there's any way to disable it right now.

[sajid-khan-afridi]

same here

[sajid-khan-afridi]

put in .gitignore file

[Safnaj]

Same for me as well. Couldn't find the answer anywhere else.

put in .gitignore file

adding it to the .gitignore file only disables its tracking. The file is annoying me and i want to get rid of this.
Its still keep generating.

[cseas]

This cache file dependency is not only annoying, but it's also a hurdle in trying to deploy the application as a non-root user in a container. Here's the related StackOverflow thread.

[Poolshark]

same...

[ricardodanaya]

same here

[vlad2710]

same here...

[silverwind]

I think it should be be put into node_modules/.cache/.eslintcache so it's out of sight like other caches (e.g. babel's).

[Blazekla]

This file is generated with react-scripts 4.0.1. If you change the version to 4.0.0 you won't have this issue for now. This might get changed in a future release.

[Ogglas]

Update:

It has now started to cause compile errors as well:

EBUSY: resource busy or locked, open 'C:\Users\Oscar\source\repos\<>\ClientApp\.eslintcache'

Original:

eslint --cache false should work but I don't know how to inject that. I saw nothing about this under Configuring ESLint or Create React App Custom Environment Variables

https://eslint.org/docs/user-guide/configuring

https://create-react-app.dev/docs/adding-custom-environment-variables/

https://eslint.org/docs/user-guide/command-line-interface#options

You could also specify another cache location if you find a way to inject the command:

--cache-location
Path to the cache location. Can be a file or a directory. If none specified .eslintcache will be used. The file will be created in the directory where the eslint command is executed.

https://eslint.org/docs/2.0.0/user-guide/command-line-interface#caching

[falinsky]

It seems that cache was enabled on purpose here: #9911

[Safnaj]

It seems that cache was enabled on purpose here: #9911

Yes bt as @silverwind said it should be there in the node_modules/.cache/.eslintcache

[silverwind]

I think the main issue is a bad default location coming from eslint, see eslint/eslint#13897.

[webdev778]

same for me.

[dominikabieder]

Not only is it annoying, it also wastes time on debugging. My app kept showing an error for the line of code that was no longer there. I tried everything and only deleting .eslintcache solved the problem.

[Motii1]

This file is generated with react-scripts 4.0.1. If you change the version to 4.0.0 you won't have this issue for now. This might get changed in a future release.

Still generates

[StraightOuttaCrompton]

A fix seems to be in progress #9977. Looks like the plan is to move .eslintcache into node_modules/.cache

[falinsky]

A fix seems to be in progress #9977. Looks like the plan is to move .eslintcache into node_modules/.cache

As far as I understand that fix has nothing to do with an issue described by @dominikabieder

Not only it is annoying, it wastes time on debugging. My app kept showing an error for the line of code that was no longer there. I tried everything and only deleting .eslintcache solved the problem.

[joescharf]

Having similar issue to @dominikabieder - Seems like when eslint fixes are applied by vscode, the .eslintcache isn't updated and eslint still complains of errors when run outside of vscode.

[silverwind]

Those sound like eslint/vscode bugs, you should report them there.

[joescharf]

Will do. In the meantime, in case anyone wanders by looking, if you're using nuxt and @nuxtjs/eslint-module, you can turn off the eslint cache in nuxt.config.js with

  eslint: {
    cache: false,
  },

[ruvesh]

This file is generated with react-scripts 4.0.1. If you change the version to 4.0.0 you won't have this issue for now. This might get changed in a future release.

Still generates

Try running npm install after changing the version. That worked for me.

[TroySchmidt]

I am having the build fail in Azure DevOps randomly with this cache file. I have added the gitignore so that it isn't in the repo. But still randomly an issue. So not sure that merely moving the location of the file is going to fix the random issue. Which feels like a race condition and back to react-scripts 0.9.2 issue.

[rafaelperozin]

put in .gitignore file

This works, but .gitignore only ignores files that are not part of the repository yet. If you already git added some files, their changes will still be tracked.

So, in this case, to ignore a file already tracked you also need to run git rm --cached .eslintcache

[VenkataJanapareddy]

We still have this issue after upgrading react-scripts from 4.0.1 to 4.0.2. We are downgrading to 4.0.0 until it's fixed.

[albert-schilling]

It is possible to disable the cache with a cli flag (--cache=false), but I can't seem to find a resource that explains how to disable the cache in the package.json or in a .eslintrc.json. Has anyone an idea?
These links did not help so far:

• https://create-react-app.dev/docs/setting-up-your-editor/#experimental-extending-the-eslint-config
• https://eslint.org/docs/user-guide/configuring/configuration-files#using-configuration-files

[howlettt]

To avoid wasting any more time debugging issues caused by this file I went with the hand grenade approach in package.json:

  "scripts": {
    "start": "del .eslintcache && react-scripts start",

[Devansh-Singh-Parmar]

Same!

[jovylle]

Same on my end. so I am forced now to uninstall it.

[jcollum]

This seems like an eslint issue, not a create-react-app issue.

[jovylle]

Yeah, same, I removed the eslint for now.

[jcollum]

@dominikabieder you may have better luck getting this resolved if you copypaste it to the eslint issues

[Probug]

mine is almost the same but a funny twist. when deployed, I get this:

Failed to compile

EACCES: permission denied, open '/home/site/wwwroot/node_modules/.cache/.eslintcache'

i have searched the web over and over again, i don't seem to find a solution to this error

[JESii]

This really too bad; if I have a typo in my code and save it, then .eslintcache doesn't get cleared and the error continues to appear in the server. The only way to remove the error is to delete .eslintcache. This is a major productivity-killer!

[mrlinnth]

Maybe related to this bug or may not. Just wanna share my experience for those having permission denied/read-only .cache/.eslintcache issue.

I also got this error just now. Looked around and found this thread, didn't really find any solution.

I tried to remove node_modules folder entirely by running 'rm -rf' which also gave same permission error.

Then I remembered that I didn't properly shut down my PC last night when I was booted into Windows.

So I boot into Windows
Did disk analyze and optimize (just to be safe, probably not needed)
Restart my PC
Boot into Linux

Fixed and no more issue for me. Just my 2cents.

[chicken-suop]

Has this really not been solved?

[jovylle]

I just managed to add it to .gitignore

[chicken-suop]

I just managed to add it to .gitignore

Yes, but as everyone says it's still being generated

[jovylle]

I have this trick I used before to block a auto generated file.

make a folder/directory
that is named ".eslintcache"
this worked on windows and that file will not proceed on generating if that folder exist.

I know this is crazy idea.

[JESii]

This is a HUGE time suck -- I keep having to re-edit/re-save my file (multiple times) and or remove that .eslintcache file (note that adding it to .gitignore does nothing to solve the problem -- the file still keeps getting generated).
NOTE: react-scripts on V4.0.0 did NOT fix the problem for me
ALSO NOTE: the directory hack mentioned above does not work
EISDIR: illegal operation on a directory, open '/Users/jseidel/ppg/hall/winter-spa/.eslintcache'
I would imagine the hours wasted by developers over this thing is mind-boggling.

[Replayattack]

mine is almost the same but a funny twist. when deployed, I get this: Failed to compile

EACCES: permission denied, open '/home/site/wwwroot/node_modules/.cache/.eslintcache'

i have searched the web over and over again, i don't seem to find a solution to this error

Hello, update your Node version in Azure to the 16 version and the error will disappear.

[thebeyondr]

🚨 Here's what worked for me

ESLint offers the option to set the cache location.

pnpx eslint "src/**/*.js" --cache --cache-location "/path/to/wherever"

Example to send that bizzatch to the shadow realm (node-modules). from a script in package.json:

{
...
"lint:fix": "eslint --cache --fix './src/**/*.{js,jsx,ts,tsx,json}' --cache-location './node_modules/@eslint/.eslintcache/'",
...
}

For 10x galaxy brain billionaire devs

ℹ️ The script above lints everything in src that's staged, keeping track of those files in a .eslintcache file we've sent to node_modules/@eslint

⚡ I use pnpm so if you use yarn, npm or whatever-package-manager-comes-out-in-the-next-half-hour your node_modules folder might look different - just find the eslint folder in there and just use that path for ---cache-location homie 🤘🏽

Gotta blast! 🚀