search

bower / registry

The Bower registry
https://registry.bower.io/packages
MIT License
292 stars 66 forks source link

Supporting plugin ecosystems #14

Closed jugglinmike closed 9 years ago

jugglinmike commented 11 years ago

I'm interested in using a package manager to foster an ecosystem of plugins for my open source library. The Bower registry already allows me to filter for packages that are named appropriately (e.g. grunt- for Grunt plugins). An additional use case that is not served by project namespacing is versioning. I would like developers to be able to quickly filter out plugins that are incompatible with the version of the library they're using.

If the registry exposed the peerDependency information specified in projects' package.json files, then the registry could be queried much more efficiently. Would this behavior be considered in-scope for Bower?

wibblymat commented 11 years ago

grunt and its plugins are npm modules, package.json is the npm metadata file (Bower's is bower.json) and peerDependencies is an npm feature that Bower doesn't have. Is it possible that you are confusing Bower with npm?

On the other hand, this sounds like a reasonable idea for the future. We would have to implement something like peerDependencies first, though, so its not likely to happen soon.

jugglinmike commented 11 years ago

Yeah, I wanted to illustrate the use case with Grunt, but since my library is intended for the browser, NPM doesn't make as much sense.

sheerun commented 9 years ago

Supporting plugin ecosystems has nothing to do with embedding peerDependencies in api responses.

And peer-dependencies don't make much sense for bower, because all dependencies are flattened.