Enable "useDefineForClassFields" in tsc --init

Search Terms

useDefineForClassFields, tsc --init, tsconfig

Suggestion

tsc --init's generated tsconfig.json should include "useDefineForClassFields": true

Use Cases

All major web and non-web engines now ship Define-style semantics.

So the safest approach is to ensure new TypeScript projects use standard web-compatible behavior.

Examples

It looks like we just need to add one line here. I am happy to send a PR.

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, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

Start in src/compiler/commandLineParser.ts near the linked tsc --init configuration. Check how generated tsconfig.json options are assembled, then add useDefineForClassFields with the requested value. Done means newly generated configurations include the option and existing generation checks, if present, still pass.