Change Request: file glob for eslint --init is hard to figure out

[krichter722]

ESLint version

7.32.0

What problem do you want to solve?

When using eslint --init on is asked Which file(s), path(s), or glob(s) should be examined?. A lot of intuitive inputs like src/**/*.(ts|tsx), src/**/*.ts and *ts all don't work for a project with .ts and .tsx files in src/ under the project root where yarn run eslint --init is executed. It's a frustrating first contact with eslint, especially since one has to start over with the questionaire and there's no link to documentation in the output and no --help for --init. The only thing I could find rtfm-wise is the issue linked below which didn't help me.

The specific error message is

No files matching the pattern "src/**/*.(ts|tsx)" were found.
Please check for typing mistakes in the pattern.

What do you think is the correct solution?

A link to the documentation in the output is slightly hard to maintain but would make a very good first impression of eslint.

It seems like --init could be a subcommand as well, i.e. eslint --init would become eslint init so that it could provide a --help. I don't like eslint --init --help because it's no a nice cli.

Participation

• I am willing to submit a pull request for this change.

Additional comments

There's another misunderstanding of the question at #7211 which has been handled as support request and been closed without improvement because it hasn't been requested by the reporter.

[nzakas]

Thanks for the feedback. Did you end up finding a glob that worked? If you did, could you share it as compared to one that didn’t work?

[krichter722]

@nzakas I went with src/**/*.ts in order to get started and get past the question. It got me past the question and started the analyses, but it was of course incomplete because the analysis from src/**/*.tsx was missing.

Upon further investigation I tried src/**/*.ts src/**/*.tsx and it seems to work based on the output Enabled a out of b rules based on n files.

However I now figured that this analysis doesn't seem to do anything or is very broken. I doesn't even get the value for indent right in a project which has a very consistent indent of 2. It seems to enable all rules which is not what I'd expect after being offered an examination of my source files, but that's a separate (set of) issue(s).

[nzakas]

Yeah, the auto config is a bit broken. I actually thought we had removed it but apparently not. In any event, I’m not surprised it doesn’t work properly with TypeScript files as that requires a custom parser and the built in rules don’t always work correctly with TypeScript.

I think we will probably move forward with removing this feature rather than trying to fix it.

[github-actions]

Oops! It looks like we lost track of this issue. What do we want to do here? This issue will auto-close in 7 days without an update.

[mdjermanovic]

Per eslint/rfcs#79, the auto-config feature will be removed in one of the future minor versions, and that's likely to be very soon (#15150), so I'm closing this issue since it only relates to auto-config.