Clientside Package Management:
an introduction to bower
what does getting jQuery look like for you?
- going to jquery.com to download?
- checkout out jQuery and building?
- remembering the URL and wget/cURL'ing it?
how bower helps
- makes installing tools easy
- uses a manifest file (
to express what to download
- downloads to a centralized place (
- resolves dependencies
wonder if there's a weather plugin?
no cloning, no copying, just ask
call weather and update the page
get our current location and run the function
why a client-side package manager
using client-side tools should be easy
- open/public code being committed into repositories
- sticking with older, buggy versions because upgrading is a PITA
- hesitancy to use exiting solutions because of the work to include them
installation via manifest file
editing the manifest file
adding to the manifest file
you can manually edit the
bower.json file, you just don't have to
in fact, bower helps out with that
say what you want, bower gets it
showdown dependency as well as the
add a dependency on the
specify we want to parse item using
- never had to hunt down angular
- was able to find a markdown module super easy
- didn't have to hunt down showdown, which module needed
- all the scripts were in a consistent place
what's coming up in bower?
- authenticate with the registration server
- update or remove published packages
- get cached copies from the server
- publish built copies if not in your repo
André Cruz & Marco Oliveira are heading up a rewrite of bower
the regular stuff
- more docs
- less bugs
- more packages
- more integration
contributing to bower
- #bower IRC channel on freenode.net
- bower google group