Enterprise Private Repositories

[jd-carroll]

This is an absolutely wonderful and truly useful project, thank you. 😊

It is also an absolutely useless project for anyone using an enterprise repository 😦. The problem is that package-json uses registry-url, which you might as well replace that library with the hard coded value https://registry.npmjs.org/.

I know registry-url can be "configured", but their suggested method really isn't practical for large enterprise use.

Would you accept a PR which uses npm-conf instead? It would address a number of issues (including #35) and enhance this project's wonderfulness!

(trying not to waste time putting together a PR that will be ignored)

Note: We are using JFrog, so all traffic is proxied through our private repo.

[naterkane]

👍 This project is useless for me as well as I use Nexus... I ended up here because npm-check depends on it... and therefore doesn't/can't work with private registries.