Option to do not override "target" and "useDefineForClassFields"

Command

build, serve

Description

There are reasons why you’ve added this warning:

TypeScript compiler options "target" and "useDefineForClassFields" are set to "ES2022" and "false" respectively by the Angular CLI. To control ECMA version and features use the Browerslist configuration. For more information, see https://github.com/browserslist/browserslist

To control ECMA version and features use the Browerslist configuration

There is no way to define target and useDefineForClassFields in the Browerslist configuration.

Please provide some option to skip target and useDefineForClassFields overriding - some projects are not ready for ES2022 and they are too big to modify overnight (or in a few weeks) to be compatible with ES2022, although they are still compatible with Angular 15 itself.

Describe the solution you’d like

Just quick ideas:

--keep-target-value --keep-use-defined-value

and

"targets": {
    "build": {
      "executor": "@angular-devkit/build-angular:browser",
      "options": {
          "keepTargetValue": true,
          "keepUseDefinedValue": true
       }
   }
}

Describe alternatives you’ve considered

No response

[mgol]

FWIW, one good reason to be able to lock to a specific target version is that some features may technically be supported by a browser but not be optimized. For example, in one code base I maintain I had to lock the target below ES2018 as object spread in Chrome is so slow it was showing performance degradation in our app perf tests: https://bugs.chromium.org/p/v8/issues/detail?id=10763

[alan-agius4]

@Splaktar, yeah thanks for pointed that out