Closed saxicek closed 9 years ago
Meh. Unless people are actually actively using the bower version of this, I'm probably going to remove it: there's zero advantage to bower over npm, and the tools you use to interact with bower are buggy and unfinished. It's just not worth the time.
But how do you tell whether people prefer npm over bower? I am using npm for server side, bower for client side. Not saying it is the best but I am just using it like that and it works for me.
But how do you tell whether people prefer npm over bower?
Ideally by comparing the download stats of the npm package versus the bower package, but since bower doesn't do statistics, I can't.
Exactly. Bower implemented anonymous statistics as opt-in feature, but because it tends to break automation, not sure what data they receive.
Given that amongst other issues I've run into, it feels like I should wait until things are stable. Really, browserify is a very very good thing.
I am using Require.js instead because I need async support for Google Maps and Analytics. It does not seem that Browserify can help with that. And it does not help with other resources such as CSS, images either (Leaflet). But it is also possible that I am doing something terribly wrong.
@tmcw stats are here: http://bower.io/stats/, what's tracked is here: https://github.com/yeoman/insight#collected-data
We're working on a per-package API so people can query stats
I get that there's a 'top modules' stats page, but there isn't a page for anything beyond the top 100 packages, right?
Sorry not yet. Coming soon though.
Closing: feel free to maintain a third-party bower package, but it adds too much friction for too little traction to be worth it for me.
Current is 0.1.0 which unfortunately does not include bower.json and Bower is then complaining about missing "main" and "ignore" entries. Since bower.json is committed in the repository already, it would be nice to release a new version to please Bower. :-)