🚀 Feature request
Command (mark with an x)
- [x] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [x] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
Description
A clear and concise description of the problem or missing capability...
Currently the CLI creates browserslist file by ng new.
The file name browserslist is a kind of deprecation. Previously, the new file name .browserslistrc was introduced.
browserslist/browserslist@7231ccd
They said browserslist is conflicting with the npx package name.
And in Angular.io, .browserslistrc is only mentioned.
https://angular.io/guide/build#configuring-browser-compatibility
Describe the solution you'd like
If you have a solution in mind, please describe it.
Generate the same file as .browserslistrc on ng new or ng generate application.
Describe alternatives you've considered
Have you considered any alternative solutions or workarounds?
Browserslist still is supporing old config file name for backward-compatibility. So workaround is not needed.
🚀 Feature request
Command (mark with an
x)Description
A clear and concise description of the problem or missing capability...Currently the CLI creates
browserslistfile byng new.The file name
browserslistis a kind of deprecation. Previously, the new file name.browserslistrcwas introduced.browserslist/browserslist@7231ccd
They said
browserslistis conflicting with the npx package name.And in Angular.io,
.browserslistrcis only mentioned.https://angular.io/guide/build#configuring-browser-compatibility
Describe the solution you'd like
If you have a solution in mind, please describe it.Generate the same file as
.browserslistrconng neworng generate application.Describe alternatives you've considered
Have you considered any alternative solutions or workarounds?Browserslist still is supporing old config file name for backward-compatibility. So workaround is not needed.