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

When using "COREPACK_NPM_REGISTRY", corepack still fetches pnpm from npmjs.org #498

Open
leo91000 opened this issue Jun 11, 2024 · 3 comments · May be fixed by #502
Open

When using "COREPACK_NPM_REGISTRY", corepack still fetches pnpm from npmjs.org #498

leo91000 opened this issue Jun 11, 2024 · 3 comments · May be fixed by #502

Comments

@leo91000
Copy link

leo91000 commented Jun 11, 2024

I have my packageManger field set to "[email protected]"

When using COREPACK_NPM_REGISTRY environment variable, corepack fetch succesfully metadata for the given package manager using the provided registry url.

However it seems that the metadata provided by the private package manager returns a tarball located on npmjs.org :

image

As a result, it downloads pnpm from npmjs.org

I am not sure if this is an issue with the private package manager of my company, or if this is some problem with how corepack interpret this.

@aduh95
Copy link
Contributor

aduh95 commented Jun 11, 2024

What version of Corepack are you using?

@leo91000
Copy link
Author

I am using corepack version 0.28.2

@devbydixon
Copy link

Its a problem with corepack. Updated my pnpm to LTS and this started popping up when I deploy to GCP. works fine locally on Mac but shits the bed in the cloud.

@aduh95 aduh95 linked a pull request Jun 13, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants