Bug: cache doesn't invalidate on plugin version upgrade

Environment

Node version: v16.15.1 npm version: N/A - using yarn Local ESLint version: 8.23.0 Global ESLint version: no global eslint installed Operating System: MacOS 12.5.1

What parser are you using?

@babel/eslint-parser

What did you do?

I upgraded eslint-plugin-react from 7.37.1 to 7.37.7.

Due to new rules addition and the cache for the former version still being used, offenses for those new rules weren’t being reported.

My code contains the following:

const Componnent = () => {
  return <table>
    <thead>
      <th align="center">title</th>
    </thead>
  </table>
}

What did you expect to happen?

Offenses to be reported

What actually happened?

Nothing was reported

Participation

• I am willing to submit a pull request for this issue.

Additional comments

Should be fixed by this PR: https://github.com/eslint/eslintrc/pull/88

[nzakas]

I think the only way we can guarantee this with the new config system is to ask plugin authors to include a version field in their plugin object, as we no longer know the package.json to read to get this info with the new config system.

[nzakas]

The eslint core loads all plugins declared in the plugins array out of the node_modules, right?

No. What you’re looking at is the code that loads the plugins from the command line --plugin flag. That is not the standard way to load plugins. Please read the documentation for the new config system: https://eslint.org/docs/latest/user-guide/configuring/configuration-files-new