NPM instance level registry - publish and install not possible

Hi Folks!

we have upgraded to the gitlab-ee 14.1.3 from 12.5 to use the NPM registry.
But i have a issue with the instance level package registry

Publishing my package to a project is working fine.
Installing with the scope:registry set to the project-url is also working fine.
But i do not want to search for the project-id everytime i want to use a npm module and set the registry for it.

So here come’s the part that doesn’t work:
I want to set the registry to the instance level:

This does not work - npm install gives the following error:
npm ERR! code E404
npm ERR! 404 Not Found - GET - Not found
npm ERR! 404
npm ERR! 404 ‘@scope/module@*’ is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

This drives me crazy.
It should work according to the documentation - also as this is given as the registry in the package detail. I have searched the topics in the forum, even watched how to videos on YT.

Is there something i have missed?

Current setup on my client:

  • Module publishConfig is set to the project repository (publish works fine)
  • Published via personal access token
  • Set the registry to instance-level url
  • Auth token for instance level + project level set in global .npmrc

When i try to call the instance level npm package url:
i get a {“error”:“404 Not Found”}

When i publish the module with the instance level url i get a 404 with the error message, that the module could not be found in the registry. As this module is new, it can’t be in the registry. Which brings me to belief that something isn’t working right with the instance level npm registry or it is me :smiley:

Any ideas how to solve this?

Thanks alot!