ESLint `import/no-unresolved` false positive when module is imported

While using ESLint, a false positive is triggered when:

using ES modules
import/no-unresolved is enabled
meow is imported (see below)

Example

Explanation

ESLint fails to detect/resolve the module because it expects the package.json main key to point to the module entry point. The existing package.json does include an exports.default key pointing to ./build/index.js, but unfortunately it is not used by ESLint.

This is obviously just a non-urgent, quality-of-life issue, but I will submit a quick PR anyway.

Workaround

Right now I'm mitigating this by having the import/no-unresolved rule ignore meow

  "rules": {
      "import/no-unresolved": ["error", { "ignore": ["meow"] }],
  }

sindresorhus / meow