npm install of private npm registry is failing

Question

I have created a private npm registry using gitlab

I have the following .npmrc file, which is the same .npmrc file that I used to publish with no issues. I've replaced all company values with placeholders.

@myorg:registry=https://gitlab.com/api/v4/packages/npm/
//gitlab.com/api/v4/packages/npm/:_authToken=[[MY_TOKEN_HERE]]
//gitlab.com/api/v4/projects/12345678/packages/npm/:_authToken=[[MY_TOKEN_HERE]]

When I go to install I get the following error message

npm install @myorg/my-package-name-here
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@myorg/my-package-name-here - Not found
npm ERR! 404
npm ERR! 404  '@myorg/my-package-name-here@latest' 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.

npm ERR! A complete log of this run can be found in:

This to me looks like it's not picking up the .npmrc file as the registry is different.

I have checked and the file is definately .npmrc and not a different extension etc.

Anyone have any ideas?

EDIT

I've done some investigation and it does look like my .npmrc file is being used, however the registry

'https://gitlab.com/api/v4/packages/npm/@myorg/my-package-name-here'

is being redirected to

'https://registry.npmjs.org/@myorg/my-package-name-here'

which is why it will be showing up as this...

It does not explain to me why it can't be found though using the auth token etc that I used to publish?

Answer 1

I've figured it out...

Everything is fine other than @myorg does not match my gitlab org name.

e.g. the gitlab url is something like this:

https://gitlab.com/my-company/...

instead it needs to match the github url, so in the above example

@my-company

After switching this it all kicked into life and I am able to get the npm package.