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
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 :
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.
The text was updated successfully, but these errors were encountered:
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.
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 :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.
The text was updated successfully, but these errors were encountered: