You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While we can point npm to a private (in-house) repository this does not affect dependencies that point to a URL instead of a package in npm. These sorts of requests are simply blocked and even if we could have them let them through the firewall we would have a dependency on a cloud resource that we do not control and therefore not have truly repeatable builds.
This is a terrible design decision on the behalf of npm itself, not actually your own issue, but it would be nice if you could find a way to avoid this sort of "non npm repository" dependency.
I raise this issue merely so you are aware of this impediment to users in strict corporate environments.
The text was updated successfully, but these errors were encountered:
ricksbrown
added a commit
to ricksbrown/adapt-cli
that referenced
this issue
Nov 3, 2016
This in your
dependencies
: "download": "git://github.com/adaptlearning/download.git" makes life very difficult in a secure enterprise environment behind a strict corporate firewall.While we can point npm to a private (in-house) repository this does not affect dependencies that point to a URL instead of a package in npm. These sorts of requests are simply blocked and even if we could have them let them through the firewall we would have a dependency on a cloud resource that we do not control and therefore not have truly repeatable builds.
This is a terrible design decision on the behalf of npm itself, not actually your own issue, but it would be nice if you could find a way to avoid this sort of "non npm repository" dependency.
I raise this issue merely so you are aware of this impediment to users in strict corporate environments.
The text was updated successfully, but these errors were encountered: