2.0.0-beta.1 now warns about files in node_modules

When I ugrade eslint from 2.0.0-alpha-2 to 2.0.0-beta.1, thousands of these warnings show up:

~/projects/my-project/node_modules/ws/index.js
  0:0  warning  File ignored because of a matching ignore pattern. Use --no-ignore to override

I’m running eslint with eslint "**/*.js" and without any ignores. The documentation states that node_modules are ignored by default, which is what I want.

From skimming through the commits, I guess this was introduced in https://github.com/eslint/eslint/pull/3948 but I don’t understand enough about the internals to look into this myself.

Thanks for helping out.

[nzakas]

We should definitely keep the < 2.0 behavior. Thanks for flagging this @gyandeeps

[IanVS]

I believe the issue is https://github.com/ember-cli/ember-cli-eslint/issues/63, but it’s unclear to me whether it’s a problem in ESLint or it is a matter of Atom’s linter-eslint not using the correct eslint executable. There’s a difficulty in that ember-cli-eslint seems to package its own version of eslint, which atom won’t pick up on in npm@2 because it is a nested dependency (https://github.com/ember-cli/ember-cli-eslint/issues/48).

As for the -d check, I wondered about that as well. Not sure why it’s there, but it seems it could be replaced with true for clarity.