Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nx@6 uses Yarn even if Npm is expicitly configred #515

Closed
DenysVuika opened this issue May 23, 2018 · 1 comment
Closed

nx@6 uses Yarn even if Npm is expicitly configred #515

DenysVuika opened this issue May 23, 2018 · 1 comment
Labels

Comments

@DenysVuika
Copy link

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.

@github-actions
Copy link

This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant