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

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

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

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

home $ bower home $ bower home <package> $ bower home <package>#<version> Opens a package homepage into your favorite browser. If no <package> is passed, opens the homepage of the local package.

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

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 $ bower prune Uninstalls local extraneous packages

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

init $ bower init Interactively create a bower.json file