aleteo.co

ojet serve windows -–browser=firefox

Launches a Windows version of the application in the Firefox browser.

ojet serve ios

Launches the application in the iOS Simulator using the Alta iOS theme.

ojet serve android --destination=emulator:MyEmulator

Launches the application in the Android emulator using the AVD named “MyEmulator”. The emulator name is case-sensitive.

ojet serve android --device

Launches the application on the attached Android mobile device.

[ios android windows]

Desired platform. Enter android, ios, or windows.

build-config

Specify the path to buildConfig.json. The buildConfig.json file contains details that Cordova can use to sign the application.

You do not need this file when building a debug version of your application for Android or Windows, or if you are building your app for deployment to an iOS simulator. However, you must configure one for testing on an iOS device and for pre-release testing of your Android, iOS or Windows application.

server-port

Server port number. If not specified, defaults to 8000.

livereload-port

Live reload port number. If not specified, defaults to 35729.

destination

Specify one of the following:

• emulator: Displays your application in the default Android AVD, iOS Simulator, or Windows Emulator.

  To use a different emulator, append its name to the emulator option: --destination=emulator:emulator-name.

  Tip:

  You can view the list of available emulators for each platform by invoking the following from your app's top-level folder:

  hybrid/platforms/{platform}/cordova/lib/list-emulator-images

  where {platform} is one of android, ios, or windows.

• browser: Displays your application in the Chrome browser on your local machine.

  If you don’t have Chrome installed or want to use a different browser, append the name of the desired browser to the browser option:

  Tip:

  To change your application’s default browser from Chrome, open oraclejetconfig.json in the application's top level directory and change the name of the browser in defaultBrowser. For example, to change the default browser to Firefox, edit oraclejetconfig.json as shown below.

• device: Sends the application to an attached device.

  Optionally, append the name of the device to device option: --destination=device:myDevice.

• server-only: Serves the application, as if to a browser, but does not launch a browser. Use this option in cloud-based development environments so that you can attach your browser to the app served by the development machine.

browser[=browser-name]

Equivalent to destination=browser[:browser-name].

emulator[=emulator-name]

Equivalent to destination=emulator[:emulator-name].

device[=device-name]

Equivalent to destination=device[:device-name].

server-only

Equivalent to destination=server-only.

livereload

Enable the live reload feature. Live reload is enabled by default (--livereload=true).

Use --livereload=false or --no-livereload to disable the live reload feature.

Disabling live reload can be helpful if you’re working in an IDE and want to use that IDE’s mechanism for loading updated applications.

build

Build the app before you serve it. By default, an app is built before you serve it (--build=true).

Use --build=false or --no-build to suppress the build if you’ve already built the application and just want to serve it.

theme

Theme to use for the application. The theme defaults to redwood for hybrid mobile applications.

Note: If you have migrated to JET 9.0.0 and later, and want to continue building with your Alta theme, for hybrid mobile themes, you can specify: alta:android, alta:ios, alta:windows). Note that the Alta theme is supported through JET 10.0.0 but is expected to become deprecated beyond that. For details about migrating applications, see Oracle JET Application Migration for Release 10.0.0.

You can also enter a different themename for a custom theme as described in About CSS Variables and Custom Themes in Oracle JET for Redwood themes and, for a migrated custom Alta theme, in Customize Alta Themes Using the Tooling.

themes

Themes to use for the application, separated by commas.

If you don’t specify the --theme flag as described above, Oracle JET will use the first element that you specify in --themes as the default theme. Otherwise Oracle JET will build the application with the theme specified in --theme.

--cssvars

Injects a Redwood theme CSS file that supports working with CSS custom properties when you want to override CSS variables to customize the Redwood theme. For details about theming with CSS variables, see About CSS Variables and Custom Themes in Oracle JET.

sass

Manages Sass compilation. If you add Sass and specify the --theme or --themes option, Sass compilation occurs by default and you can use --sass=false or --no-sass to turn it off. If you add Sass and do not specify a theme option, Sass compilation will not occur by default, and you must specify --sass=true or --sass to turn it on. For details about theming with Sass, see Work with Sass.

platform-options

Platform-specific options that will pass verbatim to the Cordova CLI.

This option is typically required for Windows device deployments or if a Cordova plugin contains multiple static libraries for different CPUs. If the value passed contains a quoted string, the quotation marks must be escaped.

For example, you can use platform-options to specify Windows architectures. By default, the architecture defaults to anycpu.