“Cannot convert undefined or null to object” after mixing eslint versions with --cache

Tell us about your environment

• ESLint Version: 5.16.0
• Node Version: 10.15.3
• npm Version: 6.9.0

What parser (default, Babel-ESLint, etc.) are you using? default

Please show your full configuration: (empty)

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

$ mkdir /tmp/test
$ cd /tmp/test
$ touch .eslintrc foo.js
$ npx eslint@5.16.0 --cache foo.js
npx: installed 117 in 5.458s
$ npx eslint@5.13.0 --cache foo.js
npx: installed 119 in 3.794s
$ npx eslint@5.16.0 --cache foo.js
npx: installed 117 in 4.248s
Cannot convert undefined or null to object

What did you expect to happen? eslint should not crash.

Are you willing to submit a pull request to fix this bug? Sure, if we can diagnose it.

[eslint-deprecated[bot]]

Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to reach accepted status after 21 days tend to never be accepted, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.

Thanks for contributing to ESLint and we appreciate your understanding.

[timabbott]

Is it intended that this bot close bugs that cause eslint to crash?