-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browserslist is ignored. #24697
Comments
The ECMA version output controlled via the browserslist configuration. In this case "ES2020" in the TypeScript configuration is ignored and hence the warning. You can set the "target" to "ES2022" in your TypeScript configuration to remove the warning. |
…ssage to be more actionable Update the `TypeScript compiler options "target" and "useDefineForClassFields" are set to "ES2022"` warning message to be more actionable. Closes: angular#24697
…ssage to be more actionable Update the `TypeScript compiler options "target" and "useDefineForClassFields" are set to "ES2022"` warning message to be more actionable. Closes: #24697
Thanks, it's clear now. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Command
build, serve, test
Is this a regression?
The previous version in which this bug was not present was
v14
Description
Browserlistrc is ignored for some reason and this warning was not present in v14.
Minimal Reproduction
Steps to reproduce
ng new *proj_name*
;target
intsconfig
toES2020
;ng serve
;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.
;ng generate config browserslist
;ng serve
;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.
.Your Environment
The text was updated successfully, but these errors were encountered: