eslint-plugin-import: import/no-unresolved is not recognizing installed modules that export "."

All dependencies are on their latest versions. Errors:

  1:39  error  Unable to resolve path to module '@vue/test-utils'  import/no-unresolved
  4:29  error  Unable to resolve path to module 'vuex'             import/no-unresolved

Code:

import { createLocalVue, mount } from '@vue/test-utils';
import axios from 'axios';
import flushPromises from 'flush-promises';
import Vuex, { Store } from 'vuex';

import { mutations } from '@/store.js';

import App from '@/App.vue';

import { currentUser } from '@@/mockData/CommonMockData.js';
import mockUsersResponse from '@@/mockResponses/Users.js';

vuex is in the dependencies and @vue/test-utils is in the devDependencies in package.json. Both are installed and in the node_modules folder.

What’s interesting is that they fail across all test files, but no other node_module imports fail. It’s just these two.

eslintrc.js

const path = require('path');

module.exports = {
  root: true,
  parserOptions: {
    parser: '@babel/eslint-parser',
    ecmaVersion: 2022,
    sourceType: 'module',
    requireConfigFile: false
  },
  extends: [
    'tjw-import'
  ],
  settings: {
    'import/resolver': {
      webpack: {
        config: {
          resolve: {
            alias: {
              '@': path.resolve(__dirname, 'src'),
              '@@': path.resolve(__dirname, 'tests')
            }
          }
        }
      }
    }
  }
};

tjw-import can be seen here:

https://github.com/tjw-lint/eslint-config-tjw-import/blob/main/index.js

About this issue

Original URL
State: open
Created a year ago
Reactions: 9
Comments: 17 (6 by maintainers)

Commits related to this issue

feat: isable `import/no-unresolved` rule due an incompatibility with package.json exports See: https://github.com/import-js/eslint-plugin-import/issues/2703 — committed to hexatool/eslint-config by MarioMH8 a year ago

Most upvoted comments

@ljharb See #1479

JounQin on Jan 7, 2024

Updated previous example to answer question

TheJaredWilcurt on Feb 7, 2023

Do they have a “main”, though?

This plugin uses resolve, which does not yet support “exports”.

ljharb on Feb 7, 2023

Yeah it’s the missing "main" field which causes an error on sql-template-tag package which appears to be ESM only and only has an exports set in the package.json

Raynos on Aug 23, 2023

👋 Just noting that I ran into this with graphql-request as well, which only has exports and not main:

...
  "exports": {
    ".": {
      "require": {
        "types": "./build/cjs/index.d.ts",
        "default": "./build/cjs/index.js"
      },
      "import": {
        "types": "./build/esm/index.d.ts",
        "default": "./build/esm/index.js"
      }
    }
  },
...

MattIPv4 on Mar 9, 2023

issue occurs also with avajs

FloV22 on Feb 14, 2023

Thank you for the head up @ljharb No "main" neither in @multiformats/multiaddr I looked at the resolve source it seems neither the legacy "module" nor "exports" is supported From Node.js 12 having only "exports" is fine, "main" is only used as a fallback when the former is missing. Since the oldest Node.js maintained LTS is 14 "exports" should be the default resolution.

PierreJeanjacquot on Feb 8, 2023

Updated issue title based on this new information.

TheJaredWilcurt on Feb 7, 2023

hey, I’m running into the same issue while importing @multiformats/multiaddr

the issue may comes from nested export of "."

@vue/test-utils

@multiformats/multiaddr

this syntax look good according to nodejs doc https://nodejs.org/docs/latest-v16.x/api/packages.html#package-entry-points but is no resolved by eslint-plugin-import

PierreJeanjacquot on Feb 7, 2023

// /node_modules/@vue/test-utils/package.json
...
  "main": "dist/vue-test-utils.js",
  "module": "dist/vue-test-utils.esm.js",
  "exports": {
    ".": {
      "default": "./dist/vue-test-utils.js",
      "require": "./dist/vue-test-utils.js",
      "import": "./dist/vue-test-utils.esm.js"
    }
  },
...

// /node_modules/vuex/package.json
...
  "main": "dist/vuex.common.js",
  "module": "dist/vuex.esm.js",
  "exports": {
    ".": {
      "module": "./dist/vuex.esm.js",
      "require": "./dist/vuex.common.js",
      "import": "./dist/vuex.mjs"
    },
    "./": "./"
  },
...

// /node_modules/axios/package.json
...
  "main": "index.js",
...

// /node_modules/flush-promises/package.json
...
  "main": "index.js",
...

The flush-promises and axios imports do not have a linting error, and do not have exports or module defined in their package.json.

TheJaredWilcurt on Feb 7, 2023