VSCode shows eslint error with '@vue/airbnb' when using webpack aliases in import paths

[KokoTa]

Version

3.0.3

Node and OS info

Node 10.7.0

Steps to reproduce

Vscode will throw error, but app running successful.

What is expected?

no error info

What is actually happening?

throw error info

---

[LinusBorg]

Please share the repository

[KokoTa]

Build with default configuration @LinusBorg

[LinusBorg]

Do npm run serve and npm run build work?

[KokoTa]

yes, running successful.

[LinusBorg]

and npm run lint ?

[KokoTa]

The same situation，app can work，but error still exist.

[LinusBorg]

So the error is only in your editor? Then I think your editor's eslint integration doesn't play nice with eslint-airbnb ?

[LinusBorg]

Possibly related: microsoft/vscode-eslint#405

[KokoTa]

I use Vscode, I don't know. OK, I try to see it.

[blitheinsz]

1 upgrade vscode editor
2 upgrade vscode-plugin ESLint to 1.7
3 ok

[2xAA]

Actually, red herring. The project folder is a subdirectory of a larger project. (SublimeLinter-)eslint was getting confused.

SublimeLinter-eslint seems to also have the same issue.

eslint version v5.12.0 (local and global)
Latest Sublime Linter and SublimeLinter-eslint

Built with vue cli 3.3.0. Vuex, Router and Airbnb linting.
node version 11.5.0.

npm run build also works fine.

[LinusBorg]

Then you should probably open an issue in their repository. We can't influence how your editor plugins work

[haoqunjiang]

No longer reproducible with the latest versions of vscode, vscode-eslint, @vue/cli…
So I'm closing this issue.

[STLighter]

Actually, red herring. The project folder is a subdirectory of a larger project. (SublimeLinter-)eslint was getting confused.

SublimeLinter-eslint seems to also have the same issue.

eslint version v5.12.0 (local and global)
Latest Sublime Linter and SublimeLinter-eslint

Built with vue cli 3.3.0. Vuex, Router and Airbnb linting.
node version 11.5.0.

npm run build also works fine.

Same problem with you! When I open the subdirectory only, everything works well. But if I open the large project, vscode shows no-unresolved error.

vscode: v1.30.2
eslint extension: v1.8.0

[TaylorDale]

Same problem with you! When I open the subdirectory only, everything works well. But if I open the large project, vscode shows no-unresolved error

Thanks for that - spent a good hour on this one trying to figure out why it wasn't resolving.

[dpgalloway]

In case anyone else is still struggling with this, I realized the same thing as others that the issue was caused by my front-end code being in a sub-directory of the main project. To fix, add this to your settings.json (change "client" to the name of your front-end sub-directory):

    "eslint.workingDirectories": [
      { "directory": "./client", "changeProcessCWD": true },
    ],