You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the upgrade the nx@6 uses yarn even if the local Angular CLI is configured to use npm. It also generates the yarn.lock file alongside package-lock.json one. And it seems to be always using yarn for new library generation.
Expected behaviour: it should be using the package manager that is configured with Angular CLI.
The text was updated successfully, but these errors were encountered:
During the upgrade the nx@6 uses
yarn
even if the local Angular CLI is configured to usenpm
. It also generates theyarn.lock
file alongsidepackage-lock.json
one. And it seems to be always using yarn for new library generation.Expected behaviour: it should be using the package manager that is configured with Angular CLI.
The text was updated successfully, but these errors were encountered: