When using the ionic CLI (v1.0.9) this are the available tasks:
serve - Start a local development server for easy app development and testing
start - Start a new Ionic project with the given name.
emulate - Emulate an ionic project on a simulator or emulator.
run - Run an ionic project on a connected device.
build - Locally build an ionic project for a given platform
platform - Configure platform targets for building an Ionic app
login - Login to the Ionic Platform
upload - Upload an Ionic project to the Ionic Platform (requires login)
Does it makes sense to build a separate CLI from Cordova one? In the Cordova CLI I can do the following which I can’t in ionic, so I guess it is not wrapping all cordova-cli tasks.
/Workspace/ionic-sidemenu$ ionic platform list
Running platform task...
Adding platform list
Platform "list" not recognized as a core cordova platform. See "platform list".
Unable to add platform list. Please see console for more info.
~/Workspace/ionic-sidemenu$ cordova platform list
Installed platforms: android 3.4.0
Available platforms: amazon-fireos, blackberry10, firefoxos, ios
In addition to this, I’m wondering about the recommended build process. In my case I have a grunt-watcher looking for source changes and then executing cordova prepare
, which triggers before_prepare
trigger which does some preparation tasks as compiling SASS, copying splashscreens, etc.
Does any of the ionic-cli task adds or extends functionality of a cordova-cli task?