Bug: package.json import results in no-missing-import

[perrin4869]

Environment

Node version: 20.14.0
npm version: 10.7.0
ESLint version: 8.57.0
eslint-plugin-n version: >=17.5.0

What rule do you want to report?

n/no-missing-import

Link to Minimal Reproducible Example

dotcore64/chai-ip#242

What did you expect to happen?

When package.json contains:

  "imports": {
    "#is-ip": {
      "node": "net",
      "browser": "is-ip"
    }
  },

and I import { isIP } from "#is-ip", the rule should pass

Participation

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

Additional comments

This regression started in 17.5.0, so probably by this PR

[scagood]

Thank you for the report, I will look later today!

[scagood]

This looks to be related to these:
webpack/enhanced-resolve#303
webpack/enhanced-resolve#310

I think the simplest solution would be a plugin that resolves the node modules to stubs, but it's a tough one.

[perrin4869]

Hm... Just curious, those are really old issues, but this regression is very recent?
As for resolving, would this be useful?
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import.meta/resolve

[scagood]

I would love to use import.meta.resolve, but we support node ^18.18.0, in fact, as soon as we can use it, we will use it!

[perrin4869]

might be worth it to fallback to the polyfill in the meantime? https://github.com/wooorm/import-meta-resolve