Closed skiadas closed 11 years ago
Thanks for the words and the tip, I'll get that set up. I think I've only added it to NPM and Jam.
Hmm, now I see why I've never paid much attention to Bower... the web really didn't need another half-baked package manager.
I've put Epoxy up there, however running bower install backbone.epoxy
won't actually work. Bower's registration command won't validate a https://
git endpoint, and their accepted git://
protocol doesn't actually install. It also looks like Bower restricts re-registering packages (so I can't correct the registration error), and there's currently no way to unregister a package (short requesting it in their GitHub issue tracker). Also as a library developer, I really dislike that it requires its own manifest file that duplicates versioning and dependency information stored in the main package.json
file. Jam does this much better by simply augmenting the package.json
schema.
I'm going to strike the bower.json
file from the Epoxy repo, and cut Bower as a loss until it matures a bit. I would request Epoxy to be removed from the Bower registry, except that I see some other data binding package has astro-turfed the name backbone.eproxy
(not cool, guys).
I'd highly recommend just going with NPM for JavaScript package management. Library developers are far less concerned with the knock-offs for good reason. You won't find as much on them, and what you do find may not be kept as up to date.
Thanks for looking into it. I agree the proliferation of package managers is somewhat annoying to say the least, and bower does have some rough corners on the developer side.
In the mean time if you want to consume epoxy via bower you can install it via bower install gmac/backbone.epoxy
or in your bower.json file like so:
{
"name": "bower",
"version": "0.0.0",
"dependencies": {
"backbone.epoxy": "gmac/backbone.epoxy#~1.0"
}
}
Sweet, thanks!
First of all, I love the package!
I was trying to incorporate it in a project and notice that Bower could not find it, have you guys thought of adding it to the bower registry? It should be as simple as adding a small manifest.json file, and then running something like
bower register <my-package-name> <git-endpoint>
.