Open joaopedronardari opened 8 years ago
Sorry Guys! kkkkkkkkkk
V2 doesn't work with bower :P
We're not planning to support bower, what's wrong with NPM exactly ?
Who's installing front-end-packages using npm?
Normally front-end-packages are installed using Bower
Bower makes versioning of built files mandatory because it relies on git instead of handling whatever it installs (as opposed to npm). I don't want built files to be versioned because of :
Not gonna happen, sorry guys. Try and use npm, it's great for front-end packages as well.
We should seriously think about an option to support Bower (via branch, github plugin for diff, commit strategy or only generating the dist for a new version automatically). I had an interesting discussion last week at the Angular JS Meetup in Vienna in favor of Bower - there are some lazyloading tools that read only from the bower_components directory. Just throwing this into this discussion - maybe there is a good compromise everyone can live with
Joking. @chaosmail if you wanna take your stab at it, go ahead :)
Good news, we are working on a solution that suits everyone. With bower support. stay tuned
Just to be clear : build files won't be published to master or any human-generated branch. The read above suggests having a separate branch to deal with Bower's need of having dist files versioned.
Add option to install by Bower dependency