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

link $ bower link $ bower link <name> [<local name>] The link functionality allows developers to easily test their packages. Linking is a two-step process. Using ‘bower link’ in a project folder will create a global link. Then, in some other package, bower link <name> will create a link in the components folder pointing to the previously created link. This allows you to easily test a package because changes will be reflected immediately. When the link is no longer necessary, s

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

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

search $ bower search $ bower search <name> Finds all packages or a specific 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

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

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

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