version

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

update

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

uninstall

uninstall $ bower uninstall <name> [<name> ..] [<options>] Uninstalls a package locally from your bower_components directory uninstall options -S, --save: Remove uninstalled packages from the project’s bower.json dependencies -D, --save-dev: Remove uninstalled packages from the project’s bower.json devDependencies

register

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

search

search $ bower search $ bower search <name> Finds all packages or a specific package.

Pluggable Resolvers

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

prune

prune $ bower prune Uninstalls local extraneous packages

login

login $ bower login Authenticate with GitHub and store credentials. login options -t, --token: Pass an existing GitHub auth token rather than prompting for username and password

lookup

lookup $ bower lookup <name> Look up a package URL by name

list

list $ bower list [<options>] List local packages and possible updates. list options -p, --paths: Generates a simple JSON source mapping -r, --relative: Make paths relative to the directory config property, which defaults to bower_components