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
pnpm config set registry --location=global fails in version 7.20.0 #5841
Comments
We can fix this. But as an alternative, you can use |
This was mainly a concern for us since it broke our build pipeline, |
In the past versions pnpm config was just passing through to npm. In v7.20 we added our own implementation. That is why it broke |
So when I use
I'll try running pnpm setup - but again this is missing in the docs :) |
OK, this one is also a bug. |
pnpm version:
7.20.0
Code to reproduce the issue:
pnpm config set registry https://pkgs.dev.azure.com/dynamicscrm/OneCRM/_packaging/ci-common-ui/npm/registry/ --location=global
Expected behavior:
Works
Actual behavior:
Unknown option: 'location'
Additional information:
node -v
prints:The text was updated successfully, but these errors were encountered: