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

Indroduce bower package #254

Open
vladimirnani opened this issue Nov 16, 2016 · 16 comments
Open

Indroduce bower package #254

vladimirnani opened this issue Nov 16, 2016 · 16 comments

Comments

@vladimirnani
Copy link

How about introducing bower package?
I find it very useful, for example for using artoo in my chrome extension i had to clone and build with gulp artoo.chrome.js.
Whereas having bower component would be much more convenient.

@Yomguithereal
Copy link
Member

Isn't npm suitable?

@vladimirnani
Copy link
Author

vladimirnani commented Nov 16, 2016

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.

@Yomguithereal
Copy link
Member

I am not opposed to publish to bower but the issue is that bower forces the developer to have a built version of the code in the repository and this is quite cumbersome. Do you know a way not to have to keep built version in the repository?

@vladimirnani
Copy link
Author

vladimirnani commented Nov 16, 2016

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 do it.

Deployment Travis

@vladimirnani
Copy link
Author

vladimirnani commented Nov 16, 2016

@Yomguithereal
Copy link
Member

Can bower target releases? In this case I could just upload the built code in the release files.

@vladimirnani
Copy link
Author

vladimirnani commented Nov 16, 2016

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

@Yomguithereal
Copy link
Member

Plus the other issue is which endpoint of the library are you using to properly load the code in your extension?

@vladimirnani
Copy link
Author

vladimirnani commented Nov 16, 2016

The way I see it is like 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 install bower-artoo-js and use only artoo.chrome.js.

@Yomguithereal
Copy link
Member

The sad thing is that npm already perform this job very well and bower applies a lot of pressure to the repositories by obliging developers to make silly things as proxy repos :-)

Your issue is that you need to ship the code with the extension I guess and that bower, by downloading the code where you need, facilitates this? But why not use a bundler like browserify or webpack to perform the same job?

@vladimirnani
Copy link
Author

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

@Yomguithereal
Copy link
Member

But if the cost is too high for you to change, I can wrap a bower version very fast. Just tell me if you really need it.

@vladimirnani
Copy link
Author

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

@duongtdvn
Copy link

I'm also interested in bower package.

@waleedsamy
Copy link

+1

@Yomguithereal
Copy link
Member

I'll try to do that soon. Ping me if I forget.

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

No branches or pull requests

4 participants