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
Ok I think I could relax this dependency since it would work with any version of Angular 1.2+. Moreover I've included some dependency that are used only in demo and that could potentially cause conflicts, so I could drop them at all and link from their cdns.
Anyway I don't know why bower would fetch beta.19 despite of what you setup in your bower.json.
I'm going to release beta.20 with a looser dependency on Angular 1.2, and i strongly advice you to use it in place of beta.14 because it has a lot of changes/fixes since beta.14 and is more close to a first release candidate. See CHANGELOG.
I am having troubling using bower to install a specific tagged version.
When I attempt to install 1.1.0-beta.14 (which is angular 1.2.16).
I end up with 1.1.0-beta.19 (which needs angular 1.2.17) causing me conflicts.
Why does bower fetch beta.19?
Some output from my install command
List cached to see what it downloaded:
The text was updated successfully, but these errors were encountered: