Typescript doc issue: document the breaking change that 2.5.0 enables useDefineForClassFields: true by default

[SohumB]

Describe the bug

useDefineForClassFields is a breaking change for codebases that rely on the old emitting behaviour. A user with such a codebase whose tsconfig.json does not explicitly set this option to false will get breakages, error messages like can't redefine non-configurable property. This should be documented as a known issue with a workaround of setting this option back to false in your tsconfig.json.

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[Shinigami92]

Are you referring to this? #4279

[SohumB]

That does appear to be the PR that introduced this behaviour, yes! It's since been published in 2.5.0.

Specifically the defaulting to true in this paragraph in plugins/esbuild.ts:

    if (loadedCompilerOptions.target?.toLowerCase() === 'esnext') {
      compilerOptionsForFile.useDefineForClassFields =
        loadedCompilerOptions.useDefineForClassFields ?? true
    }