Bug: no-extraneous-import doesn't support import maps

[privatenumber]

Environment

Node version: 21
npm version:
ESLint version:
eslint-plugin-n version: v16.4.0
Operating System: macOS

What rule do you want to report?

no-extraneous-import

Link to Minimal Reproducible Example

https://eslint-online-playground.netlify.app/#eNp1kDFvwyAQhf+KRVfH3j1371J1KRkwnCJaw9EDqlaR/3sOiCPZUjbu3uPTu3cVkfQ4D19RTEL0dVJtsi4gpU6Kl1kWaYC4WJ9Is4yeDVfpO5bhL4E3UYqp++SpmiYCjc7xHowUPbvCki/WT37cKee+MYKiCPQWkkVfSZVd6dqpD6DIQtlLsagEMTF0c0TMpOH9P0AzODR54XfR1zufeLPn/mRkzhaaCKnlNJjn8vtcv0u/8uVB6W91gcPdrZ89tVRVMgzjVuQ+h4HfVwjleK/tIVFr7smRTTy1Fk+HKh5R1xvHDJTm

What did you expect to happen?

For it to resolve the package.json import map

Participation

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

Additional comments

It only seems to check the dependency objects:

eslint-plugin-n/lib/util/check-extraneous.js

Lines 29 to 33 in 964cf65

	Object.keys(packageInfo.dependencies || {}),
	Object.keys(packageInfo.devDependencies || {}),
	Object.keys(packageInfo.peerDependencies || {}),
	Object.keys(packageInfo.optionalDependencies || {})
	)

[scagood]

Thank you for this report! I think #139 also fixes this (completely by accident) 👀

I have added a test and it seems to be covered!

[privatenumber]

Oh nice, thank you!

Out of curiosity: if pulling in enhanced-resolve to eslint-plugin-n, wouldn't there be a significant amount of overlap with https://github.com/import-js/eslint-plugin-import + https://github.com/markjm/eslint-import-resolver-enhanced-resolve ?

In what cases would someone prefer to use the import resolvers in this plugin over eslint-plugin-import?

[scagood]

mmm, that is a sound point!

I wonder if we should support the import resolver API. 🤔
I do like the extensibility of that too

[aladdin-add]

so can the plugins use the shared settings? sounds interesting! 👍