warning File ignored by default. Use "--ignore-pattern '!node_modules/*'" to override
See original GitHub issueHi
Since updating to ember 2.5 recently, I’m now getting this error:
/Users/oli/Projects/ember/node_modules/ember-freestyle/addon/modules/ember-freestyle/services/ember-freestyle.js
0:0 warning File ignored by default. Use "--ignore-pattern '!node_modules/*'" to override
Any ideas? This was working fine before.
Thanks
Issue Analytics
- State:
- Created 7 years ago
- Comments:22
Top Results From Across the Web
Eslint: warning File ignored by default. Use a ... - Stack Overflow
Your npm script runs the linter on the .eslintrc.js file and this file is as the comment says File ignored by default. You...
Read more >Developers - warning File ignored by default. Use
warning File ignored by default. Use "--ignore-pattern '!node_modules/*'" to override.
Read more >eslint/eslint - Gitter
Get 0:0 warning File ignored by default. Use a negated ignore pattern (like "--ignore-pattern '!<relative/path/to/filename>'") to override.
Read more >Ignoring Code - ESLint - Pluggable JavaScript Linter
eslintignore by default). ignorePatterns in Config Files. You can tell ESLint to ignore specific files and directories using ignorePatterns in your config files...
Read more >Configuring ESLint - ESLint - Pluggable JavaScript linter
Configuration Files - use a JavaScript, JSON or YAML file to specify configuration information for an ... By default, ESLint expects ECMAScript 5...
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
Yeah linting is still working but those warnings cause the test suite to fail.
@maoueh Yep, I’m seeing this too.
This is a tough one. It appears to be related to an issue that’s affecting all users of eslint at the moment, and I’m not quite sure it’s something we can address here (But I’d love to hear if anyone has ideas 😀).
To elaborate, briefly: Behind the scenes,
ember-cli-eslintrunseslintby way ofbroccoli-lint-eslint– which explicitly takes measures to prevent this from occurring. With atom’slinter-eslint, however, your linting pipeline is actuallylinter-eslint —> eslint, and thus it’s completely outside of anythingember-cli-eslintis doing.(Worth noting, though — especially for anyone just now getting to this issue: since the error is localized to Atom, it shouldn’t cause builds to break, as that process does still go through
broccoli-lint-eslint.)