-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with platform version resolution with Bower and 0.2.1 #440
Comments
This is the bower.json from my bower-installed polymer:
Which isn't the same as https://github.com/Polymer/polymer/blob/master/bower.json |
The reason for this mismatch is that the Polymer package in the Bower registry is In @azakus why the two different repositories with different state? |
Ugh, looks like a merge fail into the @bergie The reason there are two repos is legacy from when I've fixed the version issue in the bowerable repo, but it requires that you After that, Sorry for the inconvenience. |
@addyosmani Can you help move bower/bower#120 (comment) along so we can drop the |
#441 was caused by this too :( |
I'm seeing this quite a bit with
bower install
:So for whatever reason, it looks like Bower is resolving the dependency sometimes to 0.1.4, and sometimes 0.2.1. With 0.1.4 you get a crash when Polymer loads.
The current solution is to force dependency resolution to latest via
bower install -F
, but even then you do see this message:but at least Polymer is usable.
I've stated the Polymer dependency to
0.2.1
, and Polymer is the only package I'm using that depends onplatform
.The text was updated successfully, but these errors were encountered: