updating .eslintrc doesn't invalidate the cache

Expected Behavior

Updating linting rules/config should invalidate linting cache.

Current Behavior

When running eslint it’ll show the cached output even though .eslintrc (workspace root) was changed.

❯ nx lint akita

> nx run akita:lint 

>  NX   NOTE  Cached Output:

Linting "akita"...

Failure Information (for bugs)

Steps to Reproduce

I’m not sure when the cache kicks in, but once it does you can reproduce this.

1. nx lint stuff
2. watch cache kick in
3. add a new rule to the rules section in the root .eslintrc
4. nx lint stuff
5. observe the previous cached and now invalid response

Context

>  NX  Report complete - copy this into the issue template

  @nrwl/angular : 9.2.2
  @nrwl/cli : 9.2.2
  @nrwl/cypress : 9.2.2
  @nrwl/eslint-plugin-nx : 9.2.2
  @nrwl/express : 9.2.2
  @nrwl/jest : 9.2.2
  @nrwl/linter : 9.2.2
  @nrwl/nest : Not Found
  @nrwl/next : Not Found
  @nrwl/node : 9.2.2
  @nrwl/react : 9.2.2
  @nrwl/schematics : Not Found
  @nrwl/tao : 9.2.2
  @nrwl/web : 9.2.2
  @nrwl/workspace : 9.2.2
  typescript : 3.8.3

“eslint”: “6.8.0”, “@typescript-eslint/eslint-plugin”: “2.28.0”, “@typescript-eslint/parser”: “2.28.0”,

[vsavkin]

Sorry. The issue was marked by mistake. I removed the label.

[rarmatei]

adding "runtimeCacheInputs": ["echo .eslintrc"] doesn’t help.

After adding it I ran linting until it gave me the cached output, then I changed a rule from “off” to “warn” and ran linting again nx lint <project> but I still got the cached output

yes, I did remember to save the file 😃

Can you please try cat .eslintrc instead of echo ? Echo will print out the file name, but we want to print out the contents, so it invalidates the cache when they change (as Jack mentioned)