Support TypeScript in configuration initializer.

The version of ESLint you are using. master

The problem you want to solve. When running eslint --init, an option for TypeScript can be provided. Ref: https://github.com/eslint/eslint/issues/11368

Your take on the correct solution to problem. Add a question or option in Inquirer questions list.

Are you willing to submit a pull request to implement this change? Yes.

[platinumazure]

I’m not opposed if the team consensus is to add support to ESLint init specifically for Typescript. After all, we already explicitly ask about React. However, I’m worried about potentially having to field more requests to add support for Flow or other libraries/frameworks.

ESLint was built to get out of the business of legislating rules, and pluggability has been a core design principle in that area. But we haven’t done the same with init.

So, what I would like us to at least consider is: How can we make ESLint init more pluggable? Is there a way we could let plugins extend our init somehow? If such a thing could be implemented, then I envision typescript-eslint could export a binary in their package which might be something like, typescript-eslint-init, and they could choose to ask all, some, or none of the core ESLint init questions and add questions related to the plugin or to the language/framework/library on which the plugin is based.

[kaicataldo]

The TSC resolved this week to include a built-in TypeScript config preset and look into allowing plugins to provide additional init presets in the future.