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

Feature request: COREPACK_NPM_REGISTRY defaults to $(npm config get registry) #540

Open
zanminkian opened this issue Jul 19, 2024 · 6 comments

Comments

@zanminkian
Copy link

Currently, the default value of COREPACK_NPM_REGISTRY is https://registry.npmjs.org.
My npm registry has been changed to another one, while corepack is still using https://registry.npmjs.org.

Setting up COREPACK_NPM_REGISTRY value to follow $(npm config get registry) (the configed npm registry) is convenient, so that I don't need to concern the registry of corepack

@zyyv
Copy link

zyyv commented Jul 19, 2024

Same issue!!! 🫰 /
Although now the environment variable(process.env.COREPACK_NPM_REGISTRY) has a higher priority.

@chenlei0608
Copy link

same, how to reslove it

@zyyv
Copy link

zyyv commented Aug 1, 2024

same, how to reslove it

Set env variable: export COREPACK_NPM_REGISTRY=https://registry.npmmirror.com

@chenlei0608
Copy link

Thank you

@zanminkian
Copy link
Author

@chenlei0608 To use the same registry as npm, add export COREPACK_NPM_REGISTRY=$(npm config get registry) at the end of your .zshrc or .bashrc.

@chenlei0608
Copy link

Thanks

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

No branches or pull requests

3 participants