Virtual Packages? #350

Closed
mgutz opened this Issue Mar 28, 2013 · 1 comment

Projects

None yet

2 participants

@mgutz
mgutz commented Mar 28, 2013

Started using bower and to my surprise installing Backbone didn't pull down dependencies. I've read all the issues but the fact is bower doesn't work today for some popular packages. Ultimately it is the repo endpoint who decides or declines in the case of Backbone's benevolent dictator to add the component metadata file.

One solution is to allow virtual site packages in component.json.

{
  "name": "example",
  "version": "0.0.0",
  "dependencies": {
    "backbone": "site:backbone"
  },
  "site": {
    "backbone":  {
      "version": "1.0.x",
      "main": "backbone.js",
      "includes": [
          "https://raw.github.com/documentcloud/backbone/master/backbone.js"
      ],
      "dependencies": [
          "underscore": "~1.3",
          "jquery": "~1.9"
      ]
    }
  }
}
@necolas
Member
necolas commented Mar 28, 2013

At the moment, a shim repo is used for backbone - https://github.com/components/backbone

Yep, it's up to package authors to include the relevant manifest files, or you can just install directly from zip file, etc. We're looking at options to include a publishing model and not rely strictly on Git endpoints.

@necolas necolas closed this Mar 28, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment