Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
--ignore-pattern not working
See original GitHub issueeslint --ignore-pattern *.min.js .
the command not working, files like jquery.min.js still been linted
eslint v1.8.0, node v4.0.0
Issue Analytics
- State:
- Created 8 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Bug: Negated ignore patterns not working with ignorePatterns ...
In the .eslintrc file, I tried to ignore specific files that ends with just .test.tsx and keep linting the files which ends with...
Read more >eslint: ignore-pattern rule is not working - Stack Overflow
You specified the glob pattern incorrectly: eslint src/**/.js. With this, you are specifying: “In any directory below src, find me any files ...
Read more >Ignoring Code - ESLint - Pluggable JavaScript Linter
Lines beginning with # are treated as comments and do not affect the ignore patterns. Paths are relative to the current working directory....
Read more >ESLint --ignore-pattern is not working if file .eslintignore is not ...
Go to Settings -> Languages & Frameworks -> JavaScript -> Code Quality Tools -> ESLint · In Extra eslint options type --ignore-pattern "_.js"...
Read more >Default ignore patterns in config.xml not working - Feature
There seems to be a syncthing feature “Default ignore patterns” which should address that issue about global ignore patterns.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I got here because I’m using a (work) windows computer and forgot cmder doesn’t like single quotes.
Obviously the main problem here is windows, but the solution was to escape the double quotes e.g.
eslint --ignore-pattern \"**/*.test.js\" src/js@alansouzati This issue is from over a year ago. Since then, we have switched to .gitignore-style ignore patterns.
It’s possible the pattern is getting expanded by bash before getting passed to ESLint. Try surrounding the pattern with quotes on the command line:
If that doesn’t work, may you please create a new issue with the information in the issue template? That will make it much easier to figure out what’s going on.