CircleCI IP ranges for whitelisting access to private NPM registry



Hi, we love CircleCI - it is an awesome build tool.

We are using it to build Node projects, while running a private NPM registry. The problem is CircleCI cannot access it to pull dependencies. We could whitelist the CircleCI ip range - if we knew it. Would it be possible to have this information, even in the documentation or via a private channel?


I also have this problem @bahmutov did you ever get around it?
Any resolution from the CircleCI team?



We are facing this issue too, we are using CircleCI to to build projects that have a number of dependancies in our private npm feed.

Has there been any feedback on this?