personal configuration has been deprecated since eslint v7: https://eslint.org/docs/user-guide/configuring/configuration-files#personal-configuration-files-deprecated

please use the --config CLI option instead.

It's the same problem using --config

$ eslint . --config ~/.eslintrc.json

Oops! Something went wrong! :(

ESLint: 8.13.0

ESLint couldn't find the plugin "@typescript-eslint/eslint-plugin".

(The package "@typescript-eslint/eslint-plugin" was not found when loaded as a Node module from the directory "/home/user".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

    npm install @typescript-eslint/eslint-plugin@latest --save-dev

The plugin "@typescript-eslint/eslint-plugin" was referenced from the config file in "--config".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

maybe need to install @typescript-eslint/eslint-plugin in ~/ (to be loadable with the config)?

maybe need to install @typescript-eslint/eslint-plugin in ~/ (to be loadable with the config)?

I install the requested package (both with and without -g) and it still keeps giving the same error.

Isn't that what that does?

If not, how do I do that?

try cd ~ && npm i @typescript-eslint/eslint-plugin

try cd ~ && npm i @typescript-eslint/eslint-plugin

My home directory has to be an npm package in order for it to work? That doesn't seem like a good solution.
Shouldn't it be able to use the global npm install? (npm -g i @typescript-eslint/eslint-plugin)

just a workaround, and I agreed it's not ideal. In the early eslint, global-install usage was supported, but it's not well-designed and problematic.

another way is to use the option --resolve-plugins-relative-to.

I run npm list @typescript-eslint/eslint-plugin @typescript-eslint/parser and it shows me some versions that are not well synchronized, maybe you could check if the installed version is the same that is being cached for your .eslintrc

yarn list v1.22.19
├─ @typescript-eslint/eslint-plugin@6.6.0
├─ @typescript-eslint/parser@6.6.0
└─ eslint-config-react-app@7.0.1
   ├─ @typescript-eslint/eslint-plugin@5.62.0
   └─ @typescript-eslint/parser@5.62.0

For anyone reading this in the future: I fixed this by installing/upgrading/migrating to eslint v9, using the migrate script to convert to a new config. Wasn't flawless but worked ok.

Totally frustrating, I can't find a solution for this. I just disabled LintLens for now.