Should I remove .eslintcache when switching git branches?

user_458093 0
Viewed 4543

When you have a branch checked out and the code is linted with eslint and the --cache flag, it generates a .eslintcache file. Because the .eslintcache is in my .gitignore, when you switch to another branch and the code is linted again, the cache file is already there so eslint in theory reuses it but we cannot assume that the previous cached files are valid. So shouldn't we remove the .eslintcache file when switching branches?

eslint git
2 Answers

Could not find any suggestions on this matter, but adding .eslintcache to .gitignore is a more convinient way than deleting it manually every time

user_50149270

This is a bit of guess work - but I believe that you are fine to leave the .eslintcache in your project when you switch branches.

For a single file in .eslintcache it will have the something like the following info:

    "/path/to/project/src/components/App.js": "6",
...
  {
    "size": 538,
    "mtime": 1644596159286,
    "results": "439",
    "hashOfConfig": "434"
  },
...
  {
    "filePath": "876",
    "messages": "877",
    "errorCount": 0,
    "fatalErrorCount": 0,
    "warningCount": 0,
    "fixableErrorCount": 0,
    "fixableWarningCount": 0
  },
...
  "/path/to/project/src/components/App.js",
  [],

So it has a modified time in the cache - I assume if you switch branches then the modified time will change which should result in the cache detecting that the new files pulled in to your branch need re-linting.

I'm guessing also that the cache will delete any files that no longer exist, add any new files.

user_3270740
Related