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

Activity

1. alexeagle

   added

   type: bug/fix

   freq2: medium

   severity3: broken

   area: bazelIssues related to the published `@angular/bazel` build rulesIssues related to the published `@angular/bazel` build rules

   on Apr 27, 2019
2. alexeagle

   added this to the version 8 milestone on Apr 27, 2019
3. m-henderson commented on Apr 27, 2019

   

   m-henderson

   on Apr 27, 2019

   More actions

   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?
4. alexeagle commented on Apr 29, 2019

   

   alexeagle

   on Apr 29, 2019

   ContributorAuthor

   More actions

   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

   👍React with 👍1Reacted by Michael
5. alxhub

   closed this as completedin ff29cccon May 14, 2019
6. alxhub

   added a commit that references this issue on May 14, 2019

   fix(bazel): Use existing npm/yarn lock files (#30438)

   ...

   3136d9f
7. BioPhoton

   added a commit that references this issue on May 21, 2019

   fix(bazel): Use existing npm/yarn lock files (angular#30438)

   ...

   a327074
8. angular-automatic-lock-bot commented on Sep 15, 2019

   

   angular-automatic-lock-botBot

   on Sep 15, 2019

   More actions

   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.}
9. angular-automatic-lock-bot

   locked and limited conversation to collaborators on Sep 15, 2019
10. IchordeDionysos

    added a commit that references this issue on Jul 14, 2026

    fix(bazel): Use existing npm/yarn lock files (angular#30438)

    ...

    ff29ccc