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

RFC: Use Bower #726

Closed
tmaiaroto opened this issue Nov 24, 2013 · 1 comment
Closed

RFC: Use Bower #726

tmaiaroto opened this issue Nov 24, 2013 · 1 comment

Comments

@tmaiaroto
Copy link

I'd like to propose the use of Bower for a bunch of these 3rd party libraries... Things are already falling behind and it'll get worse. I also fear that some issues being reported may be issues with some of the third party libraries that would be remedied simply by pulling down the latest version.

It's no fun maintaining a bunch of dependencies and ensuring they are all up to date when you already have so much on your plate with your own code. So Bower would really help out in this case.

This would place things into a "bower_components" directory but you could change that destination directory I believe so it can still be "vendor" and what not. Well I know you can, but I'm not sure if you can from a bower.json config file.

Side note: You may not wish to put Twitter Bootstrap under Bower (for now) since it would likely require a move to Bootstrap 3 which would require a bit of change across the board.

@rashidkpc
Copy link
Contributor

Duplicate of #13

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

3 participants
@tmaiaroto @rashidkpc and others