register $ bower register <name> <url> Register a package

help $ bower help <command> Display help information about Bower

cache $ bower cache <command> [<args>] Manage bower cache cache clean $ bower cache clean $ bower cache clean <name> [<name> ...] $ bower cache clean <name>#<version> [<name>#<version> ..] Cleans cached packages cache list $ bower cache list $ bower cache list <name> [<name> ...] Lists cached packages

update $ bower update <name> [<name> ..] [<options>] Updates installed packages to their newest version according to bower.json. update options -F, --force-latest: Force latest version on conflict -p, --production: Do not install project devDependencies -S, --save: Update dependencies in bower.json -D, --save-dev: Update devDependencies in bower.json

version $ bower version [<newversion> | major | minor | patch] Run this in a package directory to bump the version and write the new data back to the bower.json file. The newversion argument should be a valid semver string, or a valid second argument to semver.inc (one of “build”, “patch”, “minor”, or “major”). In the second case, the existing version will be incremented by 1 in the specified field. If run in a git repo, it will also create a version commit and tag, and fail if the repo i

info $ bower info <package> $ bower info <package> [<property>] $ bower info <package>#<version> [<property>] Displays overall information of a package or of a particular version.

bower.json Packages are defined by a manifest file bower.json. This is similar to Node’s package.json or Ruby’s Gemfile. Interactively create a bower.json with bower init $ bower init Specification Detailed specification of bower.json file can be found in bower/spec repository. Maintaining dependencies Using bower install <package> --save will add <package> to your project’s bower.json dependencies array. # install package and add it to bower.json dependencies $ bower install <pa

Bower can be configured using JSON in a .bowerrc file. For example: { "directory": "app/components/", "analytics": false, "timeout": 120000, "registry": { "search": [ "http://localhost:8000", "https://bower.herokuapp.com" ] } } Placement & Order The config is obtained by merging multiple configurations by this order of importance: CLI arguments via --config Environment variables Local .bowerrc located in the current working directory All .bowerrc files upwards

Pluggable resolvers allow you to use resolvers created by 3rd party JavaScript developers — including overriding default resolvers used by Bower. For example, resolvers can be used for: Handling Mercurial or Bazaar repositories Speeding up checkouts of services like GitLab or Bitbucket Allowing to use packages from npm or component.io Proxying downloads through 3rd party service like Artifactory or Nexus Repository Implementing custom private registry (hosted on GitHub?) Adding authenticatio