-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Unable to install npm package from private registry #25924
Comments
Hi @bavoco, could you please provide more details on this issue? Is there any chance you could share the actual scope name and package name? It's somewhat hard to figure out what's going wrong if I'm not sure which parts were edited in the output you provided.
So if I get this right - the dependencies of your private package were installed correctly, but the installation of the package itself is erroring when retrieving the tarball? |
I agree this isn't much to go on, I was hoping using an empty deno cache dir and debug log would be enough information. I'll try to reproduce this with a public GitLab server later today |
I'm unable to reproduce by publishing a public (and private) package to gitlab.com. However I can consistently reproduce this issue, also on 2.0.0-rc.9, with the business GitLab server. Any ideas I can try? |
@bavoco do you have proxies involved in this setup? I'd assume so because of the business GitLab server. |
I don't know if the requests are being proxied. To see if it's caused by the tar, I pointed to the tar file in the package.json and that doesn't install it. Does Deno support specifiying a tar in the package.json? |
For now I can work around the issue with a fetch and @std/tar (very nice that it supports web streams) |
@bavoco not currently, no.
That's great to hear. I'm eager to look into this issue as soon as you can provide some more info. I'm gonna remove it from Deno 2.0 milestone for now. |
I got the same issue. We have a private repo in gitlab and when i try to install with the same .npmrc that works with node i get the same message as op. We dont have any proxy envolved. What kind of information do you need? @bartlomieju |
FYI you can upgrade to |
Version: Deno 2.0.0-rc.7
OS: Windows 11
package.json
deno.json
.npmrc
When I run deno install, the output is:
The resulting node_modules folder looks like:
Notice that it did download the dependencies of the package I was trying to install. So although it says it could not find a package tarball, it definitely did find something at the url and it is using the authtoken from the npmrc correcly otherwise it would have had a 404.
The output of `DENO_DIR=C:/TEMP/deno DENO_LOG=debug deno install` is:
The text was updated successfully, but these errors were encountered: