search

Hacklone / private-bower

A simple private bower registry
Other
667 stars 131 forks source link

redirecting to public bower #208

Open luckyabhishek opened 8 years ago

luckyabhishek commented 8 years ago

I understand that private bower acts as a proxy to public bower in case I use bower install any-public-package. However in some cases I have seen that the bower client ends up downloading the nested dependencies directly from public bower repository. We have a situation where private bower can be accessed without using a proxy while the public downloads have to be through an authenticated proxy. This makes it almost impossible to work with private-bower as I can't have a single bowerrc file with and without a proxy :). Is this a known issue ? Or a desgin decision ? What's my option ?

donny-dont commented 8 years ago

I'm seeing a similar situation. I wanted to use private-bower as an optimization for our build servers so they hit something closer. I'm only seeing some of the dependencies in the private-bower listing. The rest seemed to have gone through other means.

Is there a way to run bower to stop this behavior?

donny-dont commented 8 years ago

Nevermind it seemed to hit github if it was setup to a Github url.

So for reference @luckyabhishek 

# Hits private-bower
"dependencies": {
  "polymer": "~0.5.1",
}

# Hits github
"dependencies": {
  "polymer": "Polymer/polymer#~0.5.1",
}