initalizing config with values

Suggestion

🔍 Search Terms

–init options

✅ Viability Checklist

My suggestion meets these guidelines:

• This wouldn’t be a breaking change in existing TypeScript/JavaScript code
• This wouldn’t change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn’t a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript’s Design Goals.

⭐ Suggestion

Allow --init to be used with compiler flags, so you can make a tsconfig.json with non-default values in a single command.

📃 Motivating Example

You can make a tsconfig.json with non-default values, making it easier to initialize TS projects.

💻 Use Cases

I use a bash alias/function to initialize my projects, and there’s no easy way to set the outDir to a non-default value, it would be nice to have this feature so its much easier.

[ghost]

pog i got good first issue

[andrewbranch]

So is the current status that all compilerOptions keys can already be specified but no root keys like include, exclude, files, references can? Each of these keys is an array type and include and exclude values commonly include globs that will be evaluated by the shell if not quoted. I’m not sure these are actually very good candidates for specifying on the CLI.