Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish to Bower #40

Open
juandopazo opened this issue May 5, 2014 · 5 comments
Open

Publish to Bower #40

juandopazo opened this issue May 5, 2014 · 5 comments
Assignees

Comments

@juandopazo
Copy link

@kriskowal I noticed you were reluctant to publish to Component. Do you feel the same way about Bower? It'd be very useful to those relying on it for CI.

@kriskowal
Copy link
Owner

I do feel the same way about Bower, if not more so. Q was working on Bower by coincidence for a long while, but when I stopped using UMD, stopped checking in the non-CommonJS build products, and started publishing versions of version 2 under the experimental tag, the Bower users downstream were suddenly out of luck and had to lock their version explicitly like q#1.0.1. It seems to me that Bower needs to get its act together to play well with npm.

@kriskowal
Copy link
Owner

I am now considering Bowser support. I did a thing called Q-Git based on JS-Git that lets me pretty easily commit build products directly to branches or tags. I might take this approach to building ASAP for Bower, complete with bowser.json, directly to the version tag when I publish. The key is that publishing needs to be one command and no redundancy in the source.

@juandopazo
Copy link
Author

😲 That's brilliant!

@sethlivingston
Copy link

+1

@deepaksisodiya
Copy link

any update?

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

No branches or pull requests

4 participants