-
Notifications
You must be signed in to change notification settings - Fork 88
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
Refuses to lint anything under node_modules
#336
Comments
Honestly, no idea ... just some idea. We actually don't read "eslintignore" or any configuration files. So it just all may rely on the working dir? If you enable debug for SublimeLinter -- use the Command Palette for that, then watch it in Sublime's console -- it will show the exact command plus the working dir we're using here. That might give a first hint. Maybe it can't find the "eslintignore" file from there. 🤞 |
Appreciate the reply. Confused by two things:
So it does or doesn't look for/read |
🙄 It's my own command. You have to manually set it in the SublimeLinter settings. Sorry. (Or install my command: https://github.com/kaste/SublimeLinter-addon-toggler) We don't evaluate eslintignore, but we send eslint the filename of the view, and eslint should look it up, shouldn't it. Have you maybe used
in your SublimeLinter settings at some point because that does a similar thing (and also allows negation using |
eslint 8.56.0
Works great for anything not under
node_modules
Will not lint automatically nor by manual linting for anything under
node_modules
.eslintignore
contains!**/node_modules/**
!node_modules
Running
eslint .
from terminal outside of Sublime reportsnode_modules
files as expectedThe text was updated successfully, but these errors were encountered: