Documentation bug: Re: linting node_modules
#13006
Labels
archived due to age
This issue has been archived; please open a new issue for any further discussion
documentation
Relates to ESLint's documentation
The version of ESLint you are using.
6.8.0
The problem you want to solve.
Per https://eslint.org/docs/user-guide/command-line-interface , there is an implied need to ignore
node_modules
(which seems no longer to be the case per #1163):node_modules
seems implicit here as well:The first line is confusing as it seems to suggest one cannot get linting of
node_modules
orbower_components
yet it is possible to reenable both of them with!
.Your take on the correct solution to problem.
node_modules
from the examples unless to point out that one can undo the default (it may be helpful to mention that!.eslintrc.js
(or!.*.js
) can be added back too, at least until eslint 7 may change this behavior for!.eslintrc.js
).node_modules
(orbower_components
) by adding!node_modules/**
to an ignore (within an.eslintignore
file or by a command such as$(npm bin)/eslint --no-inline-config --ignore-pattern='!node_modules/**' .
). (I truly hope this functionality will never be dropped, btw!)Are you willing to submit a pull request to implement this change?
Not at this time.
The text was updated successfully, but these errors were encountered: