By default it uses the first layer in the profile to bundle all the modules for the application
You can specify the layer you want to target by passing -appConfigLayer "layer/name" on the command line
You can make sure a layer per-view is built instead of a single layer for all the app by having the multipleAppConfigLayers: true set to true in your profile. This is useful if you have a lot of views that won't get navigated to in a typical usage of your application. In that case you might not want to load everything upfront.
Limitations:
it does not support the "./" shortcut notation to reference the modules in the config file. Indeed this is relative to the application root this is not necessarily where the config file is located. The consequence of this is that it also does not support the default location of a view module as this is based on "./" shortcut mechanism. This does not sound too problematic to me as anyway I think at some point we might want to get rid of this (see: https://docs.google.com/document/d/1fe2qm1x_AHidYd2wNkG77tZgFIrvlt-ctGT0rpb-5F0/edit#heading=h.1ci8z4eiigaz)
it does not support multiple config files. However thanks to #104, I hope we can have a single config entry point.
This is an implementation of enhancement #108. It comes with a modified version of the layoutApp test to show how to use it.
Use from layoutApp directory is:
Options:
Limitations: