eslint: Get rid of warning ignored files

Hi, i have a question. After bump of sass-loader we need to use sassOptions in our next.config.js, but when i change it, like sassLoaderOptions: { sassOptions: { includePaths: ['public/assets/styles'] } }

and try to commit to github, eslint gives me 0:0 warning File ignored because of a matching ignore pattern. Use "--no-ignore" to override

Our default eslint is yarn run eslint --fix --max-warnings=0

Is there some way to ignore this warning?

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 16 (6 by maintainers)

Most upvoted comments

Hey there, sorry to hijack this thread but I’m dealing with a similar issue:

Here’s the situation: Due to changes in v9, lint-staged now passes a list of all changed files to eslint (instead of a configurable subset), some of which I do not want to be linted (hence I ignore them with my .eslintignore). Eslint throws warnings that I am trying to lint ignored files:

/Users/taoh/Sites/lims/server/src/data-lib-lims/entities/user/deleteNestedUserRecords.js
0:0  warning  File ignored because of a matching ignore pattern. Use "--no-ignore" to override

Is there a way for eslint to suppress warnings that files are being ignored?

Do we need to add another CLI option to get around this? Does one already exist?

Here is the original issue in lint-staged: https://github.com/okonet/lint-staged/issues/711

tnrich on Oct 10, 2019