-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using local eslint, not global #197
Comments
ESLint always prefers a local installed version over a global installed one. Can you provide a workspace that demonstrate the problem since I am not able to reproduce this locally. |
Well.. It was just my mistake. Sorry! |
I'm having the same problem. The eslint command in the terminal is running from global location, not local. I'm using vscode version 1.10.2 and eslint extension 1.2.8. |
The eslint command in the terminal is honor your path setting which very likely point to the global one. You can always run the local one using |
Thanks! That worked. I defined the following task for running eslint:
Could you confirm if this is correct? I couldn't find any documentation on creating a task for this extension. |
I updated the doc to provide an example for an eslint task. It looks like this
|
I installed eslint in global and local workspace. but I want to use local eslint in this extension. Is there any options about it?
The text was updated successfully, but these errors were encountered: