Open vladimirnani opened 7 years ago
Isn't npm
suitable?
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 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?
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.
Good example how it can be done: Publishing Angular Autowrap to npm, bower and GitHub Releases from Travis-CI
Can bower target releases? In this case I could just upload the built code in the release files.
Hm not sure, it can target git tags. Is that sufficient?
Plus the other issue is which endpoint of the library are you using to properly load the code in your extension?
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
.
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?
Ok. Yes agree, these proxies seem to be redundant.
Maybe it is time to switch to npm
+ webpack
from bower
+ gulp
.
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.
No problem for me to switch. Thanks. Lets just wait if there will be anybody thats really needs that, otherwise close issues.
I'm also interested in bower package.
+1
I'll try to do that soon. Ping me if I forget.
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.