drop eslint-plugin-import

[arily]

Clear and concise description of the problem

Hi,
I am running into an issue with TS5.0 extends.

My tsconfig.json

{
  "extends": ["./.nuxt/tsconfig.json", "./tsconfig.base.json"]
}

will cause an error:

Oops! Something went wrong! :(

ESLint: 8.43.0

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received an instance of Array
Occurred while linting /repo/nuxt.config.ts:2
Rule: "import/default"
    at new NodeError (node:internal/errors:399:5)
    at validateString (node:internal/validators:163:11)
    at Object.join (node:path:1172:7)
    at loadTsconfig (/repo/node_modules/tsconfig-paths/lib/tsconfig-loader.js:93:39)
    at loadSyncDefault (/repo/node_modules/tsconfig-paths/lib/tsconfig-loader.js:40:18)
    at tsConfigLoader (/repo/node_modules/tsconfig-paths/lib/tsconfig-loader.js:26:22)
    at readTsConfig (/repo/node_modules/eslint-plugin-import/lib/ExportMap.js:818:528)
    at isEsModuleInterop (/repo/node_modules/eslint-plugin-import/lib/ExportMap.js:821:277)
    at ExportMap.parse (/repo/node_modules/eslint-plugin-import/lib/ExportMap.js:808:317)
    at ExportMap.for (/repo/node_modules/eslint-plugin-import/lib/ExportMap.js:807:201)

related issues/prs:

• Using Typescript 5.0's array extends in tsconfig causes an error while linting import-js/eslint-plugin-import#2751
• [Deps] upgrade tsconfig-paths to ^4.0.0 import-js/eslint-plugin-import#2447
  in short: Maintainers of eslint-plugin-import decided to prioritize support node 4 over Typescript 5

Suggested solution

switch to eslint-plugin-i

Alternative

here are some hacks mentioned in the related issues:

• Using Typescript 5.0's array extends in tsconfig causes an error while linting import-js/eslint-plugin-import#2751 (comment)
• Using Typescript 5.0's array extends in tsconfig causes an error while linting import-js/eslint-plugin-import#2751 (comment)
• [Deps] upgrade tsconfig-paths to ^4.0.0 import-js/eslint-plugin-import#2447 (comment)

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[antfu]

PR welcome :)

[arily]

#205

here you go

[baixiaoyu2997]

Just a reminder for users who want to switch to multiple values for extends. Although the related pull request has resolved this issue, you may still encounter the "TypeError: value.replace is not a function" error when using @commitlint. Please refer to: TypeStrong/ts-node#2000 for more information.

[fxzer]

我遇到了相同的问题，请问怎么解决呢？
I have encountered the same problem, how can I solve it?