New in version 1.9.
Manage bower packages with bower
parameter | required | default | choices | comments |
---|---|---|---|---|
name |
no | The name of a bower package to install | ||
offline |
no |
|
Install packages from local cache, if the packages were installed before | |
path |
yes | The base path where to install the bower packages | ||
production (added in 2.0) |
no |
|
Install with --production flag | |
relative_execpath (added in 2.1) |
no | Relative path to bower executable from install path | ||
state |
no | present |
|
The state of the bower package |
version |
no | The version to be installed |
description: Install "bootstrap" bower package. - bower: name=bootstrap description: Install "bootstrap" bower package on version 3.1.1. - bower: name=bootstrap version=3.1.1 description: Remove the "bootstrap" bower package. - bower: name=bootstrap state=absent description: Install packages based on bower.json. - bower: path=/app/location description: Update packages based on bower.json to their latest version. - bower: path=/app/location state=latest description: install bower locally and run from there - npm: path=/app/location name=bower global=no - bower: path=/app/location relative_execpath=node_modules/.bin
For more information on what this means please read Extras Modules
For help in developing on modules, should you be so inclined, please read Community Information & Contributing, Helping Testing PRs and Developing Modules.