Frequently Asked Questions

My app works without the aggregator but fails when using it. How can I debug the problem?

The aggregator supports various query args that invoke debugging features. These query args are supported when debug or development mode are enabled. To use the query args, you need to be able to propagate query args specified in the URL for your application to the aggregator loader extension config. See the sample application's test.html and loaderConfig.js to see how this may be done. The following query args can be used to help debug your application:

optimize

Value can be simple (default), whitespace, or none. Controls the level of optimization/minification performed on JavaScript and CSS files.

showFilenames

If true

noCache

If true, then the aggregator will ignore any cached data and build the response from scratch. It will also include the Cache-Contrl:no-store header in all aggregator responses.

expandRequire

If value = log, then diagnostic information related to require list expansion will be written to the browser's JavaScript console

hasBranching

If false(default = true), then has! plugin branching will not be performed.

The debugging query args are disabled by default, but can be enabled by specifying one of the following console commands: ``` aggregator setoption developmentMode true ``` or ``` aggregator setoption debugMode true ``` Alternatively, if you don't have access to an OSGi console, you can add ```developmentMode=true``` or ```debugMode=true``` to aggregator properties file. See [Options](../wiki/Options) for more details, and for descriptions of the features enabled by debug and development modes.

Note: depending on the console command processor installed in your OSGi framework, the command separator can be either a space or a colon. To see which separator you need to use, try entering the commands aggregator help and aggregator:help. The examples in this page all use the space separator, but if your command processor uses the colon, then you should adapt the examples accordingly.

You can also try enabling loader debugging by setting the dojo-error-api and dojo-trace-api features, as well as specifying loader trace logging options (see the trace property in loaderConfig.js.