Enterprise Private Repositories
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.
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too