Closed fernandofleury closed 7 years ago
Thanks @fernandofleury, is it possible this could be related to https://github.com/AtomLinter/linter-eslint/issues/610?
Hi @IanVS thanks for the quick reply. Yes, it looks like. Let me explain a bit further:
I have an alias on webpack to app/assets/client/
, and was referencing the config with the webpack import/resolver. after changing to the node import/resolver:
"import/resolver": {
"node": {
"paths": ["./app/assets/client"]
}
}
I suppose I should close this issue (since it looks like a duplicate) and open one at eslint-import-resolver-webpack right?
Issue Type
Question
Issue Description
I've a different output of
linter-eslint
versuseslint cli
. It's complaining along with theeslint-plugin-import
on the init of every single file:and also with the usage of
eslint-import-resolver-webpack
it's not being able to resolve my alias (as shown on the last line of the print)Maybe I'm missing something?
Bug Checklist
eslint
CLI gives the proper result, whilelinter-eslint
does notLinter Eslint: Debug
command from the Command Palette below