-
Notifications
You must be signed in to change notification settings - Fork 165
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] support fetch COREPACK_NPM_REGISTRY from http protocol REGISTRY #293
Comments
We use a private npm registry in the company, but it uses the http protocol so we can't use corepack to enable pnpm, hope to support http. |
Our current approach is to replace the https module introduced by corepack with the http module. |
I'm also attempting to do this, though with a different setup. I'm trying to sandbox package installs of untrusted code using docker and gVisor. I am cutting off the network while still allowing access to the registry by running a local verdaccio instance on the non-internet network that is attached to my sandbox container. verdaccio is running as an http service; while I can configure yarn, npm, etc to use that instance just fine, I can't install the package managers themselves when corepack is in use because corepack rejects the http protocol (even though that's all I have). |
I need to download packagemanager from private http npm registry.
There's an error when I execute the command
COREPACK_NPM_REGISTRY="http://npm.mycompany.com/" corepack prepare pnpm@8.6.12
Error
Notice that all packagemanagers(npm, pnpm and yarn) support download package through custom registry with http protocol.
Maybe we can support download packagemanagers from custom REGISTRY with http protocol?
corepack/sources/httpUtils.ts
Lines 9 to 27 in b8a4a52
If possible, I can work with the issue.
Enviroment
The text was updated successfully, but these errors were encountered: