6.0.0-alpha.1 tries to process configuration files in ignored directories

[Standard8]

Tell us about your environment

• ESLint Version: 6.0.0-alpha.1
• Node Version: 8.16.0
• npm Version: 6.4.1

What parser (default, Babel-ESLint, etc.) are you using?
default

Please show your full configuration:

Configuration

Top-level .eslintrc.js

module.exports = {
    "parserOptions": {
        "ecmaVersion": 2017
    },
};

Top-level .eslintignore

test/**

For test/.eslintrc.js

module.exports = {
  "extends": [
    "prettier",
  ]
};

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

No source code necessary (I had an index.js that was commented out).

./node_modules/.bin/eslint .

What did you expect to happen?

No errors

What actually happened? Please include the actual, raw output from ESLint.

$ ./node_modules/.bin/eslint .

Oops! Something went wrong! :(

ESLint: 6.0.0-alpha.1.
ESLint couldn't find the config "prettier" to extend from. Please check that the name of the config is correct.

Normal files within ignored directories are correctly ignored, but it seems that the .eslintrc.js files are still processed.

Are you willing to submit a pull request to fix this bug?
No

[mysticatea]

Thank you for your report.

Actually, this is intentional behavior because we change the order of loading; now ESLint loads config files before target files. The purpose of this change is to configure target files with config files. For example, eslint/rfcs#20, eslint/rfcs#22. With either proposal, we can add the .eslintrc.js as a lint target with the config file. ESLint needs to load config files when ESLint entered into directories while traversing in order to realize such a feature.

If you used test instead of test/** to ignore the directory, we lose the ability to unignore any files in the directory with negative file patterns, so ESLint doesn't enter the directory. (Actually, test/** means to ignore all files in the test directory, but not the test directory itself.)

[Standard8]

Ok, I think that makes sense, thank you for the response.

If nothing else, I'd suggest this is flagged in the breaking changes, and maybe also adding an example to the configuration section around ignoring files. There's probably not too many people with sub-directory imports in this fashion, but the solution wasn't immediately obvious to me.

[eslint-deprecated]

It looks like the conversation is stalled here. As this is a question rather
than an action item, I'm closing the issue. If you still need help, please send
a message to our mailing list or
chatroom. Thanks!
[//]: # (auto-close)