Vladimir Nani

It is suitable, but i just wonder how better organize, because in my chrome extension I have `bower` as package manager for client side modules.

I think the way to go is to have a publish task in travis. Also agree that having built version in repo is cumbersome. I could investigate how we can...

Good example how it can be done: [Publishing Angular Autowrap to npm, bower and GitHub Releases from Travis-CI](http://zpbappi.com/publishing-angular-autowrap-to-npm-bower-and-github-releases-from-travis-ci/)

Hm not sure, it can target git tags. Is that sufficient?

The way I see it is like [bower-angular-animate](https://github.com/angular/bower-angular-animate). And we would list build output here. Bower user will specify which endpoint of library he needs. In my case i would...

Ok. Yes agree, these proxies seem to be redundant. Maybe it is time to switch to `npm` + `webpack` from `bower` + `gulp`.

No problem for me to switch. Thanks. Lets just wait if there will be anybody thats really needs that, otherwise close issues.