ESM: Unable to resolve path to module 'got' import/no-unresolved

[mahnunchik]

Unable to resolve path to module 'got' import/no-unresolved

// Unable to resolve path to module 'got'  import/no-unresolved
import got from 'got';

• got v12.0.0
• eslint v8.5.0
• eslint-plugin-import 2.25.3

[ljharb]

Do you have it installed? Are you getting that warning on the command line, or just in your editor? Is eslint installed locally, and not globally?

[mahnunchik]

"dependencies": {
    "got": "^12.0.0"
  },
  "devDependencies": {
    "@babel/core": "^7.16.5",
    "@babel/eslint-parser": "^7.16.5",
    "eslint": "^8.5.0",
    "eslint-config-airbnb-base": "^15.0.0",
    "eslint-plugin-import": "^2.25.3"
  },
"eslintConfig": {
    "parser": "@babel/eslint-parser",
    "extends": [
      "airbnb-base"
    ],
    "parserOptions": {
      "ecmaVersion": 2021,
      "requireConfigFile": false
    }
  }

[ljharb]

Thanks, but that doesn’t answer my questions. Resolving requires everything be present in node_modules.

[mahnunchik]

Do you have it installed?

Yes

Are you getting that warning on the command line, or just in your editor?

Comandline and editor (vs code).

Is eslint installed locally, and not globally?

Locally, fresh install.

[ljharb]

Thanks!

In this case, the latest version of got drops support for CJS, and as such, can’t be resolved by our CJS-only resolution mechanism. If you’re using native ESM, this plugin won’t help you, because it’s designed for use with CJS, or transpiled ESM (Babel/TS).

If you downgrade to got v11, or switch to a package author that isn’t user-hostile, then you should see everything resolve correctly.

[mahnunchik]

ESM should work. CJS should be deprecated.

[ljharb]

That’s a strong and wildly incorrect opinion.

Native ESM has tons of downsides and offers no benefits over CJS. Both are first-class module systems in node, so yes, native ESM should work, but the ecosystem isn’t ready to support it yet.

I’m going to close this.

[nghiepdev]

Same issue with type-fest

import {Except} from 'type-fest';

Unable to resolve path to module 'type-fest'.eslintimport/no-unresolved

[ljharb]

Same problem, caused by the same maintainer - altho in that case, it doesn't have any runtime values, so you should be using import type.

[jsg2021]

Those modules that the no-unresolved rule fails to find appear to be missing main and only defining exports (as node documents).

[ljharb]

@jsg2021 yes, see #2331 (comment)

[jsg2021]

@ljharb sorry :} I was just deep in my own research trying to assist my finding. Forgot to double-check the thread. I've been lucky that I'm only now having to sort with these modules.