Error caching npm package from gitlab private registry

[JarekToro]

Version: Deno 2.1.6

Seems to be related to #25924
But either was not entirely fixed by #26473 or has since regressed. But I believe it is the latter as It also failed on 2.0.3

.npmrc

@privateregistryname:registry=https://gitlab.company.engineering/api/v4/packages/npm/
//gitlab.company.engineering/api/v4/packages/npm/:_authToken=XXXXXXX

deno.json

{
  "imports": {
    "@privateregistryname/package-name": "npm:@privateregistryname/[email protected]"
  }
}

Command

deno install
error: Failed caching npm package '@privateregistryname/[email protected]'

Caused by:
    Could not find npm package tarball at: 
https://gitlab.company.engineering/api/v4/projects/4055/packages/npm/@privateregistryname/package-name/-/@privateregistryname/package-name-1.0.0.tgz_

[marvinhagemeister]

I just tried it out and I can both publish and install packages from the GitLab npm registry without any issues.

Is the domain correct? Is the project id correct? Does the package with the matching version exist in the registry?

[JarekToro]

The domain is correct. Upon further debugging. Deno seems to have problems when using gitlab instance level registry setup.

example:

@privateregistryname:registry=https://gitlab.company.engineering/api/v4/packages/npm/

However it does work when using a project level registry setup

example:

@privateregistryname:registry=https://gitlab.company.engineering/api/v4/projects/4055/packages/npm/ 

[marvinhagemeister]

Right, I was only trying out the project level setup.

[JarekToro]

@marvinhagemeister Does this ticket need anymore info?

[marvinhagemeister]

no