[ng add]: support for dev dependencies

[dirkluijk]

🚀 Feature request

Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [X] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Description

For our library, we want to provide schematics for the ng add command. However, this automatically installs our library as dependency. Shouldn't there be a way to install it to the devDependencies?

We do add our library to the devDependencies our selves (using schematics), but that results in the following warning:

Installed packages for tooling via npm.
    ✅️ Added "foo" into devDependencies
    🔍 Installing packages...
UPDATE package.json (980 bytes)
npm WARN The package foo is included as both a dev and production dependency.

Describe the solution you'd like

• Support for an additional dev option: ng add mylib --dev.
• Update the npmInstall() task with an additional dev: boolean argument.

This could be done in a backwards compatible way.

Alternative solution

• Let ng add perform an npm install --no-save
• Change the package.json ourselves

This might be breaking.

[mgechev]

This feature makes sense to me. Especially with ng deploy there could be more and more dev dependencies that folks want to add to their projects.

Thanks for the PR as well!

[dirkluijk]

There are several articles out there, about how to write your own ng-add schematic, but what I understand is that you don't need to run the addPackageJsonDependency() yourself? At least not for the package that is installed right?

[alan-agius4]

Hi all, this has been addressed via #15815

[alan-agius4]

You don't need to run addPackageJsonDependency() because it will be added to the dependencies via https://github.com/angular/angular-cli/blob/master/packages/angular/cli/tasks/npm-install.ts

[angular-automatic-lock-bot]

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.}