Command line tools which make developing Tabris.js apps even easier.
npm install -g tabris-cli
tabris init
... will guide you through creating a Tabris.js project structure in the current directory.
tabris serve
... will start a server you can point the Tabris.js developer app to.
Request logging can be enabled using the option --logging
or -l
.
tabris build [android|ios|windows]
... will perform a local app build. When run for the first time, it prompts for a build key, which can be retrieved from the Tabris.js Account Settings page.
The build type (debug or release) can set by adding either --debug
or --release
, while debug is the default.
The options --device
and --emulator
specify whether the app should be built for/ran on a device or an emulator.
The option --verbose
will provide more verbose output.
In addition to the build
command, the CLI supports a run
command which behaves in the same manner as build
but also deploys and starts the built app on a connected device or an emulator:
tabris run [android|ios|windows]
Variables in the config.xml
are replaced by environment variables unless --no-replace-env-vars
is given.
Additional variables can be specified with the --variables
option:
tabris build [android|ios|windows] --variables FOO=bar,BAR=baz
will replace all occurrences of $FOO
with bar
and $BAR
with baz
.
For code signing, you can specify a build config file (see: iOS, Android) using the --cordova-build-config=...
option. It can be relative to the cordova/
project directory. You may want to include this file in .gitignore
since it could contain sensitive information.
To speed up the build, pre-compiled build artifacts are being reused. To clean up the build cache, e.g. after adding or updating Cordova plug-ins, call:
tabris clean
Published under the terms of the BSD 3-Clause License.