| 1 | Synopsis
|
| 2 |
|
| 3 | cordova-cli config <command> [options]
|
| 4 |
|
| 5 | The config command can be used to set, get, delete, edit, and list global cordova options.
|
| 6 |
|
| 7 | Options
|
| 8 | --set <key> <value> ... Sets the config key to the value. If value is omitted, then it sets it to "true".
|
| 9 | --get <key> ........... Echo the config value to stdout.
|
| 10 | --delete <key> ........ Deletes the key from all configuration files.
|
| 11 | --edit ................ Opens the config file in an editor.
|
| 12 | --ls .................. Lists contents of config file.
|
| 13 |
|
| 14 |
|
| 15 | Syntax
|
| 16 | cordova-cli config set <key> <value> ....... cordova config set autosave true
|
| 17 | cordova-cli config get <key> ............... cordova config get autosave
|
| 18 | cordova-cli config delete <key> ............ cordova config delete autosave
|
| 19 | cordova-cli config edit .................... cordova config edit
|
| 20 | cordova-cli config ls ...................... cordova config ls
|
| 21 |
|
| 22 | Options
|
| 23 | autosave ...................... default setting = true
|
| 24 | Allows the user to set save to true or false when adding platforms or plugins.
|
| 25 | When false, platforms/plugins are not saved to `config.xml` and `package.json`.
|
| 26 |
|
| 27 | browserify ...................... default setting = false
|
| 28 | Allows the user to use the browserify module to bundle the JavaScript files of
|
| 29 | the included plugins at build time versus our traditional run time loading of
|
| 30 | those files.
|
| 31 |
|
| 32 | Examples
|
| 33 | cordova config set autosave false
|
| 34 | cordova config set browserify true
|