Proxied packages from npmjs.org don't get full metadata
anacronw opened this issue · comments
The way it works right now prevents new updates from registry.npmjs.org for packages that were initially fetched remotely. In the cases where we have a 404 from artifactory and npm-artifactory must proxy the request, it should not save that data back into artifactory for caching. Requests for package metadata not explicitly published to artifactory should be fetched remotely.