Skip to content

Issues with platform version resolution with Bower and 0.2.1 #440

Description

@bergie

I'm seeing this quite a bit with bower install:

screenshot 2014-03-08 at 15 56 23

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:

screenshot 2014-03-08 at 15 52 40

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 on platform.

Activity

  1. forresto commented on Mar 8, 2014

    @forresto

    This is the bower.json from my bower-installed polymer:

    {
      "name": "polymer",
      "description": "Polymer is a new type of library for the web, built on top of Web Components, and designed to leverage the evolving web platform on modern browsers.",
      "homepage": "http://www.polymer-project.org/",
      "keywords": [
        "util",
        "client",
        "browser",
        "web components",
        "web-components"
      ],
      "author": "Polymer Authors <polymer-dev@googlegroups.com>",
      "version": "0.2.1",
      "main": [
        "polymer.js"
      ],
      "dependencies": {
        "platform": "Polymer/platform#0.1.4"
      }
    }
    

    Which isn't the same as https://github.com/Polymer/polymer/blob/master/bower.json

  2. bergie commented on Mar 8, 2014

    @bergie
    Author

    The reason for this mismatch is that the Polymer package in the Bower registry is components/polymer. In there for 0.2.1 we have platform 0.1.4 as the dependency

    In Polymer/polymer the dependency is set correctly to 0.2.1.

    @azakus why the two different repositories with different state?

  3. dfreedm commented on Mar 8, 2014

    @dfreedm
    Member

    Ugh, looks like a merge fail into the components/polymer repo.

    @bergie The reason there are two repos is legacy from when Polymer/polymer was a source repository and not just builds. It is a manual process to change where the endpoint is.

    I've fixed the version issue in the bowerable repo, but it requires that you bower uninstall polymer, then bower cache clean polymer platform.

    After that, polymer will install with the correct version of platform.

    Sorry for the inconvenience.

  4. dfreedm commented on Mar 8, 2014

    @dfreedm
    Member

    @addyosmani Can you help move bower/bower#120 (comment) along so we can drop the components/polymer repo?

  5. dfreedm commented on Mar 10, 2014

    @dfreedm
    Member

    #441 was caused by this too :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions