The import-x/no-unresolved rule conflicts with the alias of the vite alias path

[WZDreamJiao]

I am very sorry to bother you. During the project construction process, I used eslint-plugin-import-x to make import rules, and used resolve.alias to configure path aliases in the vite configuration file. Unfortunately the import - x/no - unresolved this rule, does not identify the import HelloWorld from '@ / components/HelloWorld. Vue' the introduction of this path, I was looking for, but didn't find effective solution, Sorry to bother you again

[WZDreamJiao]

package.json:
"eslint-import-resolver-typescript": "^3.7.0",
"eslint-plugin-import-x": "^4.5.0",

vite.config.ts：
export default defineConfig({
plugins: [vue(), Unocss()],
resolve: {
alias: {
'@/': resolve('src/'),
},
},
})

eslint.config.js:
{
rules: {
'import-x/no-nodejs-modules': [
'error',
{ allow: builtinModules.map(mod => node:${mod}) },
],
'import-x/no-unresolved': ['error', { ignore: ['^virtual:'] }],
},
},
{
// Have no effect
settings: {
'import/resolver-next': [
createTypeScriptImportResolver({
project: 'tsconfig.json',
alias: {
'@/': './src/',
},
extensions: ['.js', '.ts', '.vue'],
}),
],
},
},

App.vue:

<script setup lang="ts"> import HelloWorld from '@/components/HelloWorld.vue' </script>

Error:
Unable to resolve path to module '@/components/HelloWorld.vue'.eslint[import-x/no-unresolved]

[SukkaW]

@WZDreamJiao Have you tried this import resolver for vite alias? https://github.com/pzmosquito/eslint-import-resolver-vite

[WZDreamJiao]

@SukkaW Thank you very much. It works. I'll look into how it works. Thank you very much

[SukkaW]

You can have multiple resolvers enabled all at once with import-x/resolver-next options, and the resolver should execute in order.

[WZDreamJiao]

@SukkaW yes，thank you