warning File ignored by default. Use "--ignore-pattern '!node_modules/*'" to override

See original GitHub issue

Hi

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:open
  • Created 7 years ago
  • Comments:22

github_iconTop GitHub Comments

1reaction
oligriffithscommented, May 18, 2016

Yeah linting is still working but those warnings cause the test suite to fail.

On 18 May 2016, at 07:51, Brian Sipple notifications@github.com wrote:

It looks like this traces back to a behavior in eslint where warning messages for default-ignored files were being output. But then it also appears that this behavior has been removed as of eslint@2.10.2. I’m thinking we might just need to update the version of eslint being used under the hood by broccoli-lint-eslint – or configure it in a similar manner.

As for the file generation discrepancies, @oligriffiths, .eslintrc.js and tests/.eslintrc.js are now the intended starting points. I added a note to CHANGELOG.md to clarify that.

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub

0reactions
BrianSipplecommented, Jun 9, 2016

@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-eslint runs eslint by way of broccoli-lint-eslint – which explicitly takes measures to prevent this from occurring. With atom’s linter-eslint, however, your linting pipeline is actually linter-eslint —> eslint, and thus it’s completely outside of anything ember-cli-eslint is 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.)

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found