1. Developing Oracle JET Apps Using Virtual DOM Architecture
  2. Properties in the oraclejetconfig.json File

A Properties in the oraclejetconfig.json File

The oraclejetconfig.json file supports a range of properties that you can configure to determine the behavior of your Oracle JET project.

Note:

Where Property is <prop>.<subprop> it indicates that <subprop> is a subproperty of <prop>. For example, paths.components means "paths": { "components": "value" }.

Table A-1 Properties in the oraclejetconfig.json File

Property Value Type Valid Values Default Notes
architecture String mvvm or vdom mvvm Type of app architecture.
components Object component name/version value pairs No default value exists for this property.

Component name/version value pairs for components to be restored from the component exchange upon ojet restore. Similar format to a package.json. For example:

"components": { "oj-doceg-double-picker": "^2.0.0" }

bundleName String simple file name with a .JS extension bundle.js Allows an override of the default name used for an optimized app.
bundler String webpack | <any> No default value exists for this property.

In release 11.0.0, JET introduced bundler-only support for Webpack. If webpack was specified as the value for the bundler property, the before_webpack hook was used to bundle the app. Otherwise, the before_optimize hook managed the RequireJS-based app bundling. Webpack-based bundler applied only to the app bundling. Custom component optimization continued to use RequireJS-based bundling, and could be configured with the before_component_optimize hook.

In release 12.0.0, JET introduced end-to-end Webpack support. With the --webpack argument in an ojet create command, Oracle JET creates an ojet.config.js file where you configure Webpack usage. No bundler property is configured in the oraclejetconfig.json file.

defaultBrowser String browser name chrome Sent to Apache Cordova when serving hybrid mobile apps as --target when the destination is browser.
defaultTheme String redwood, redwood-notag, stable redwood

Name of theme to use as the default in the app.

dependencies Object component name/object or version number pairs No default value exists for this property.

Names of potential component or pack dependencies used to check whether certain pre-minified components should be excluded from the ojet build --release bundling process. For example:

"dependencies": { "oj-pack-comp": { "version": "2.0.0"} }

Or

"oj-comp": "2.0.0"

exchange-url String URL No default value exists for this property.

Component exchange instance for publishing components. For example:

https://exchange.url.com/api/0.2.0

Note:

This setting can also be inherited (if not present) from a global value defined through ojet configure --exchange-url=<addr> --global which will be stored centrally (for example, .ojet/exchange-url.json)
generatorVersion String Oracle JET CLI version No default value exists for this property. Deprecated. Historical information about the version of JET that was first used to create the project. Not used by the CLI.
installer String yarn or npm npm If specified, an alternate installer to run instead of the default npm for npm install type commands.
localComponentsSupport boolean true/false No default value exists for this property. Indicates whether the component exchange backend supports the local components extension. The value will be recorded by the CLI in oraclejetconfig.json. If a user wants to opt out of the local components support, they can set this value to false deliberately.
paths.components String path jet-composites

Path where locally-created components are stored relative to a root that is dependent on the scaffolded project type:

  1. Project created with --vdom or --template=basic-vdom template. Root will be src/ .
  2. Project created with --typescript. Root will be src/ts/ .
  3. Default project. Root will be src/js.

Note:

In a a project created with the vdom basic template or --vdom option, this value will be pre-set to just components rather than the default jet-composites.
paths.exchangeComponents String path exchange_components Folder where components added from the exchange are stored for new virtual DOM apps. Non-virtual DOM apps (MVVM) use the older jet_components when this is not set. This path must be a simple folder name which will be created in the root of the project as a peer of the src/ folder.
paths.source.common String path src Simple folder name relative to the project root. A folder hierarchy cannot be used here. Other settings such as paths.components will be relative to this location.
paths.source.hybrid String path src-hybrid Simple folder name relative to the project root. A folder hierarchy cannot be used here.
paths.source.javascript String path js Simple folder name relative to the defined src folder. A folder hierarchy cannot be used here. Other settings such as paths.components may be relative to this location in the relevant project type.
paths.source.styles String path css Simple folder name relative to the defined src folder. A folder hierarchy cannot be used here.
paths.source.themes String path themes Simple folder name relative to the defined src folder. A folder hierarchy cannot be used here.
paths.source.tsconfig String path   If specified, this subproperty enables the relocation of the tsconfig.json file from its default location at the app root. Simple folder name relative to the defined src folder. A folder hierarchy cannot be used here.
paths.source.typescript String path ts Simple folder name relative to the defined src folder. A folder hierarchy cannot be used here. Other settings such as paths.components may be relative to this location in the relevant project type.
paths.source.web String path src-web Simple folder name relative to the defined src folder. A folder hierarchy cannot be used here.
paths.staging.hybrid String path hybrid Path where the hybrid build products are generated.
paths.staging.themes String path staged-themes Path where themes are staged.
paths.staging.web String path web Path where the web build products are generated.
sassVer String semver-style version number 5.0.0 node-sass npm package version that will be installed if sass is added
stripList Array of strings path strings No default value exists for this property. List of .gitignore-style paths to strip when ojet strip is executed. This bypasses the list in the .gitignore file.
unversioned boolean true/false false

When true, Oracle JET generates components in a directory path without the component version number when you run ojet build or ojet serve. For example:

appRootDir/web/components/my-component-pack/my-widget-1/

Without the unversioned property or with "unversioned": false (the default), the output path is:

appRootDir/web/components/my-component-pack/1.0.0/my-widget-1/

The unversioned entry in the oraclejetconfig.json file takes precedence over the Oracle JET command-line argument (--omit-component-version). That is, if the oraclejetconfig.json file includes "unversioned": false (include component version number in the directory path) and you build your Oracle JET app using the following command, Oracle JET includes the component version in the generated directory path:

ojet build --omit-component-version
watchInterval String Number of milliseconds 1000 Configure the interval at which the live reload feature polls the Oracle JET project for updates by configuring a value for this property. The default value is 1000 milliseconds.