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
7.21.0 release not ignoring node_modules ? #14158
Comments
The default pattern is |
Thanks for the quick follow up. Adding It looks like the
The debug output is quite large, I'll try to just share the relevant parts of it if thats OK
|
This Do you have a pattern like Adding another This probably wasn't noticed before v7.21.0 as the symbolic links in
Is there another sequence of |
You are totally right @mdjermanovic , I've located a Thanks ! Hopefully anyone else experiencing this problem will find this issue, I suspect I'm not the only one |
As it turns out, this I'll submit an issue there and see what they think about adjusting it |
For anyone stumbling onto this, this will be fixed in an upcoming version of ember-cli Until then you can add the |
Node version: v14.15.5
npm version: v6.14.11
Local ESLint version: v7.21.0 (Currently used)
Global ESLint version: Not found
Operating System: Linux (ubuntu variant)
What parser (default,
@babel/eslint-parser
,@typescript-eslint/parser
, etc.) are you using?I think
@babel/eslint-parser
?What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
Upgraded from eslint 7.20.0 to 7.21.0, then ran the command below;
yarn eslint .
What did you expect to happen?
No eslint errors when upgrading from eslint 7.20.0 to 7.21.0
What actually happened? Please copy-paste the actual, raw output from ESLint.
Eslint errors in node_modules (ignore the warnings, tonnes of those in the app)
Steps to reproduce this issue:
yarn eslint .
in the application directoryThese errors are solved by either;
node_modules/
to .eslintignore (which the https://eslint.org/docs/user-guide/configuring/ignoring-code says should be ignored by default)Are you willing to submit a pull request to fix this bug?
The text was updated successfully, but these errors were encountered: