eslint：无法解析模块“src/interfaces”的路径

Question

I'm having a very similar problem here and have tried every answer with no luck: Using eslint with typescript - Unable to resolve path to module

Here is a screenshot of the linting error:

tsconfig.json

{
  "compilerOptions": {
    "allowJs": true,
    "allowSyntheticDefaultImports": true,
    "baseUrl": "./",
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "isolatedModules": true,
    "jsx": "react",
    "lib": ["esnext", "DOM"],
    "module": "esnext",
    "moduleResolution": "node",
    "noEmit": true,
    "noFallthroughCasesInSwitch": true,
    "noImplicitReturns": false,
    "resolveJsonModule": true,
    "skipLibCheck": true,
    "strict": true,
    "target": "esnext",
    "useUnknownInCatchVariables": true
  },
  "exclude": ["node_modules", "babel.config.js", "metro.config.js", "jest.config.js"],
  "include": ["src"]
}

eslintrc.json

{
  "settings": {
    "import/resolver": {
      "node": {
        "extensions": [".js", ".jsx", ".ts", ".tsx"],
        "paths": ["src"]
      }
    },
    "react": "React",
    "version": "detect"
  },
  "env": {
    "browser": true,
    "es6": true,
    "jest": true,
    "node": true
  },
  "extends": [
    "eslint:recommended",
    "airbnb",
    "prettier",
    "plugin:import/typescript",
    "plugin:@typescript-eslint/eslint-recommended",
    "plugin:@typescript-eslint/recommended"
  ],
  "globals": {
    "Atomics": "readonly",
    "SharedArrayBuffer": "readonly"
  },
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "allowImportExportEverywhere": true,
    "ecmaVersion": "latest",
    "sourceType": "module",
    "ecmaFeatures": {
      "jsx": true
    }
  },
  "plugins": ["react", "@typescript-eslint", "prettier", "jest"],
  "rules": {
    "array-element-newline": ["error", "never"],
    "camelcase": "off",
    "comma-dangle": ["error", "only-multiline"],
    "complexity": ["off"],
    "consistent-return": ["off"],
    "import/unresolved": ["off"],
    "import/extensions": ["off"],
    "jest/no-disabled-tests": "warn",
    "jest/no-focused-tests": "error",
    "jest/no-identical-title": "error",
    "jest/prefer-to-have-length": "warn",
    "jest/valid-expect": "error",
    "jsdoc/require-jsdoc": ["off"],
    "linebreak-style": ["off"],
    "max-len": ["error", {"code": 350, "tabWidth": 2}],
    "max-nested-callbacks": ["off"],
    "new-cap": ["off"],
    "no-console": ["warn"],
    "no-dupe-keys": ["error"],
    "no-nested-ternary": ["off"],
    "no-use-before-define": ["off"],
    "no-useless-catch": ["off"],
    "no-var": ["error"],
    "quotes": ["error", "single"],
    "react/display-name": ["off", {"ignoreTranspilerName": true}],
    "react/jsx-filename-extension": [1, {"extensions": [".js", ".jsx", ".tsx"]}],
    "semi": ["error", "always"],
    "@typescript-eslint/camelcase": "off",
    "@typescript-eslint/no-unused-vars": ["off"],
    "@typescript-eslint/explicit-module-boundary-types": ["off"],
    "@typescript-eslint/no-explicit-any": ["off"]
  }
}

prettierrc.json

{
  "bracketSpacing": false,
  "jsxBracketSameLine": true,
  "singleQuote": true,
  "eslintIntegration": true,
  "trailingComma": "es5",
  "endOfLine": "auto",
  "printWdith": 120
}

Answer 1

I'm not sure why but removing the airbnb from the extends solved the issue.

change eslintrc.json from:

  "extends": [
    "eslint:recommended",
    "airbnb",
    "prettier",
    "plugin:import/typescript",
    "plugin:@typescript-eslint/eslint-recommended",
    "plugin:@typescript-eslint/recommended"
  ],

to

  "extends": [
    "eslint:recommended",
    "prettier",
    "plugin:import/typescript",
    "plugin:@typescript-eslint/eslint-recommended",
    "plugin:@typescript-eslint/recommended"
  ],

I hope one day there is a global linting file that will allow us to just use 1 so conflicts aren't creating these headaches.