I'm trying to setup a npm remote registry inside Artifactory. While the registry works perfectly direct with npm, using Artifactory as proxy results in 404 error on a npm install.
Looking at the Artifactory debug logs I could figure out Artifactory ignores the tarball location of the npm package from the metadata and tries to get the package on a specific location after getting the metadata is successfully.
Repository URL: https://example.com/api/v4/packages/npm/
Package Name: @jfrog/test-package
On a client side npm install:
1. Artifactory tries to get the metadata of the package first:
2. Artifactory tries to download the npm packages:
Answer: 404 Not Found
Artifactory ignores the tarball location and tries to get the package at
I would expect that Artifactory tries to download the artifact here: https://example.com/api/v4/projects/1886/packages/npm/@jfrog/test-package/-/@jfrog/test-package-0.1.12.tgz It's the URL inside npm metadata of the artifact location.