@angular/bazel always generates WORKSPACE with yarn_install even if ng used npm

[alexeagle]

By default I do ng new, ng add @angular/bazel, I have a package-lock.json file but bazel fails because it looks for yarn.lock instead

[m-henderson]

so basically we should check to see if npm was used and if it was we need to look for a package-lock.json instead of yarn.lock?

[alexeagle]

Workaround is to create projects with yarn
ng config -g cli.packageManager yarn
or manually change the WORKSPACE file produced by the @angular/bazel schematic to use npm_install in place of yarn_install

The fix is for the schematic to be written with an npm_install rule if npm was used, yes