Skip to content
This repository has been archived by the owner on Jun 15, 2021. It is now read-only.

Support installing packages for alternative repositories #159

Open
rvagg opened this issue Sep 6, 2012 · 0 comments
Open

Support installing packages for alternative repositories #159

rvagg opened this issue Sep 6, 2012 · 0 comments

Comments

@rvagg
Copy link
Member

rvagg commented Sep 6, 2012

npm is a great fit for Ender but I know a lot of people are very uncomfortable with it for front-end packages. There's also a few alternative front-end repositories popping up that we could consider supporting.

1.0-wip has all the repo code abstracted into repository.js so in theory it wouldn't be too hard to add support for additional repositories. The reliance on the node_modules directory and packages.json might be a bit of an issue though, although most of that logic is fairly well partitioned too.

The new Bower from Twitter is the first logical target and I've been looking into that, Jam is another. Volo could be considered too but I'm not sure it has a particularly bright future.

Thoughts on how to support alternative repositories:

  • --repository npm|bower|jam|volo command line argument, with npm being the default.
  • add a repository designator to the package names, so you might do something like: ender build npm:underscore bower:jquery bower:bootstrap. Though, mixing repositories in a single build may be problematic, particularly when it comes to dependency resolution and duplication (perhaps it's just a case of caveat emptor?).


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant