ng-add forces use of NPM to install dependencies even when another package manager is configured in angular.json

[FabienDehopre]

When you install the package using ng add @testing-library/angular and you have configured another package manager than NPM, the install phase fails.

In the code of the ng-add schematics, the packageManager has a default value set to "npm".

angular-testing-library/projects/testing-library/schematics/ng-add/index.ts

Line 35 in e0cd81e

export function installDependencies(packageManager = 'npm') {

I think if you don't pass the packagerManager option, the NodePackageInstallTask task should use the package manager configured in the angular.json file, right?

[timdeschryver]

Oops, my bad... I can't remember why it's like that.
It can be replaced with:

context.addTask(new NodePackageInstallTask());

Do you want to create a PR for this @FabienDehopre ?

[FabienDehopre]

Sure! I'll do it this weekend.