Which @angular/* package(s) are relevant/related to the feature request?
No response
Description
Current Behavior
In Angular v22, the default and recommended TypeScript/ECMAScript target remains ES2022. While it is technically possible to use newer ECMAScript features, the ES2022 target leads to downleveling, reduced runtime optimization, and lack of official support for emitting modern JavaScript aligned with current runtimes.
Expected Behavior
Angular should officially support and validate newer ECMAScript targets (e.g., ES2023, ESNext)
Proposed solution
-
Allow Angular CLI to fully support newer target values (e.g., ES2023, ESNext) without requiring workarounds
-
Update documentation to reflect compatibility with modern runtimes
-
Provide guidance on when it is safe to move beyond ES2022
Alternatives considered
NA
Which @angular/* package(s) are relevant/related to the feature request?
No response
Description
Current Behavior
In Angular v22, the default and recommended TypeScript/ECMAScript target remains ES2022. While it is technically possible to use newer ECMAScript features, the ES2022 target leads to downleveling, reduced runtime optimization, and lack of official support for emitting modern JavaScript aligned with current runtimes.
Expected Behavior
Angular should officially support and validate newer ECMAScript targets (e.g., ES2023, ESNext)
Proposed solution
Allow Angular CLI to fully support newer target values (e.g., ES2023, ESNext) without requiring workarounds
Update documentation to reflect compatibility with modern runtimes
Provide guidance on when it is safe to move beyond ES2022
Alternatives considered
NA