🐛 Bug: Flat config causes eslint-plugin-import error message

[KristjanESPERANTO]

Bug Report Checklist

• I have tried restarting my IDE and the issue persists.
• I have pulled the latest main branch of the repository.
• I have searched for related issues and found none that matched my issue.

Expected

I'm using the recommended rules of eslint-plugin-import also for checking eslint.config.js. I just added eslint-plugin-package-json according to the README instructions to the config like this:

import eslintPluginImport from "eslint-plugin-import";
import packageJson from "eslint-plugin-package-json/configs/recommended"; // added

I wouldn't expect any complaints from the import plugin when I import eslint-plugin-package-json.

Actual

Now when I run eslint I get the import rule no-unresolved throws that error message:

error    Unable to resolve path to module 'eslint-plugin-package-json/configs/recommended'  import/no-unresolved

eslint-plugin-package-json works nevertheless.

I have no other problems with the import plugin, so I guess there is a problem with the way eslint-plugin-package-json is imported.

Additional Info

No response

[JoshuaKGoldberg]

Hmm, this might be import-js/eslint-plugin-import#2495. Have you tried with eslint-plugin-import-x?

[KristjanESPERANTO]

I didn't know eslint-plugin-import-x before, but I just tested it. Saddly the same problem appears:

error    Unable to resolve path to module 'eslint-plugin-package-json/configs/recommended'  import-x/no-unresolved

It seems, that the issue is the same in eslint-plugin-import and eslint-plugin-import-x and not in your package. So we can close this issue?

I'll deactivate the rule for now.

[JoshuaKGoldberg]

Yeah agreed. It's unfortunate but given that the path resolution does work at runtime, I'm not inclined to do a deep dive into other plugins' issues.

Thanks for filing though! If someone else sees this then, hey, maybe they'll have info to support or dispute this conclusion. 😄