Repository navigation
bug(schematics): adding package to devDependencies #32630
Description
Is this a regression?
- Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
ng add @angular/material adds package @angular/material in devDependencies section of package.json
Reproduction
Steps to reproduce:
- Create a new angular app
- Run
ng add @angular/material
Expected Behavior
I would expect @angular/material to be added to dependencies section only, not in devDependencies
Actual Behavior
@angular/material is being added to both sections dependencies and devDependencies
Environment
- Angular: 21.2.0
- CDK/Material: 21.2.0
- Browser(s): -
- Operating System (e.g. Windows, macOS, Ubuntu): macOS
Activity
crisbeto commentedon Feb 28, 2026
This is likely a behavior change in the CLI, we only add the package to the
dependencies: https://github.com/angular/components/blob/main/src/material/schematics/ng-add/package-config.ts#L37. I'm guessing we add it to thedependenciesand then the CLI comes around and adds it to thedevDependenciestoo. I'll transfer the issue.fix(@angular/cli): correct dev dependency detection logic in `ng add`
fix(@angular/cli): correct dev dependency detection logic in `ng add`
fix(@angular/cli): correct dev dependency detection logic in `ng add`
angular-automatic-lock-bot commentedon Apr 2, 2026
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.