Error `unable to resolve path to module. eslint import/no-unresolved` but only in VSCode, not in ESLint CLI

[alexleboucher]

I upgraded the package eslint-import-resolver-typescript from 3.7.0 to 4.2.1 and VSCode ESLint shows errors unable to resolve path to module. eslint import/no-unresolved on my imports.

I created an issue on the eslint-import-resolver-typescript repo (import-js/eslint-import-resolver-typescript#396) but as the error is related to VSCode and not ESLint CLI, the main contributor suggested me to create an issue on your repository.
The package uses a napi module: rspack-resolver under the hood.

You can easily reproduct the issue by cloning my project : docker-express-postgres-boilerplate and upgrading the library eslint-import-resolver-typescript

[dbaeumer]

I am not able to reproduce this

Any additional things I need to do?

[thewilkybarkid]

I'm seeing something similar. I'm also seeing:

(There's one of these for each of the import/* rules enabled.)

This could be a macOS-only problem?

[alexleboucher]

Yes, I'm on mac.

Nope, no additional things you need to do. I only have to upgrade this library and I see errors...

[hyorimitsu]

I'm also facing the same issue. It seems to be reproducible when upgrading eslint-import-resolver-typescript to version 3.9.0 or later. For reference, I'm also using a macOS.

[alexleboucher]

I am not able to reproduce this

Any additional things I need to do?

I saw you tagged the issue as info-needed. Is someone in the repo team able to reproduce it now?

[renchap]

I am also facing this issue. It happens for the non-relative imports that use aliases defined in tsconfig.json, and only for the non-type imports somehow:

If I run eslint manually from this file in the terminal, it does work correctly.

I am using a monorepo, with "eslint.workingDirectories": [{ "pattern": "./packages/*/" }].

Is there a way to get more information to understand what is different between eslint ran from the VSCode extension vs from the CLI?

[dbaeumer]

@renchap do you have a GitHub repository I can clone that demos this. May be I can reproduce it there. Without being able to reproduce the error it is very hard to say what is the root cause of this.

[Serhansolo]

Hi, I am also facing this issue!

You don't need a repo, just install vue with create vue (npm create vue@latest)

I have a fresh installation of Vue with vue-create. I am therefore using the flat-config.

With these settings (w/o OxLint):

For some reason, the default installation of Vue does not use the '@' alias. Once I change the imports to use the alias, I see the mentioned error.

Vue comes with a default eslint.config.ts file. In my new project, I tried numerous setups. With the TS config file. Using the Vue helpers and also a config from scratch… I noticed that sometimes, for pure random reasons, the IDE does resolve the paths… but after a while, it stops working.

--EDIT--

Using the same command, I created a Vue project without TS.

The CLI creates an eslint.config.js file instead. With this setup, it does work.

I hope you can locate the issue… Because the issue is definitely in the vscode plugin for ESLint. When running ESLint in the CLI in both setups, I get the expected results. As in, no import errors.

--EDIT--
I use a Windows x64 machine, by the way.

[dbaeumer]

@Serhansolo I would really prefer a GitHub repository I can clone. This ensures that I do use the same exact content and settings as you do. This repository should also contain you local VS Code settings if you changed any.

[Serhansolo]

Ah, gotcha.

I will get to it asap. I am occupied right now. I will make a report with all relevant local settings also. I will put those in a settingsfile in the repo..

[Serhansolo]

Okay, I cannot believe this. I just arrived at my workplace only to realize that the screenshots I took earlier were fixed by elves. I cannot reproduce it anymore.