-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Manage client-side dependencies using Bower #6369
Comments
a couple things here. Qunit we want to be under dependencies along with jshint so that tests can be done without the users need to install bower or npm ( the jshint wont be until we switch to make our quint tests run it #6364 ). As to hashchange. im not sure i have a strong opinion on this one way or the other. |
Updated jshint on the above list. About not needing to run
Good, because using bower now to point to @gseguin's branch (the same one of the upstream PR) has the benefit of making the future transition (for upstream lib) smoother. |
@rxaviers yes sorry should have mentioned that yes we plan to commit the dependencies to maintain the ability to run tests and demos out of the box |
:) |
Manage the following frontend dependencies using a tool (eg. bower). Based on whole team discussion about a consistent way of managing frontend dependencies across all projects.
dependencies:
devDependencies:
1: About jquery.hashchange.js modification that is not yet upstream. Can we use @gseguin modified clone in the bower config, eg.
"hashchange": "gseguin/jquery-hashchange"
?The text was updated successfully, but these errors were encountered: