Build Logs
Last updated
Last updated
Depending on the size and complexity of an application you are developing, you may require access to the build logs and output that occurs during a deploy (e.g. when pressing CTRL/CMD+S). Build logs allow you to see how your code is being compiled and further allow you to debug an application which fails to deploy.
OXIDE has the ability to automatically bring up build logs when you perform deploy operations. When this is enabled, OXIDE will intelligently place the panel in a floating panel contained within a collapsed tray allowing you to follow along with a build while not disrupting your workspace. It will look like this:
To enable this feature, search for the setting below and make sure it is enabled:
As per the setting, this will only show the output when one or more build operation for a deploy action fails.
To enable this feature, search for the setting below and make sure it is enabled:
Both settings are also available in the Settings panel under the Editing category:
To access the build logs for deploys which happened in the past, do the following:
Navigate to the relevant deploy event in the Deploy logs:
2. Expand the deployment operations information:
3. Click on one of the build operation 'pills' to see more information:
This will bring up a panel that shows the verbose output for each build operation step.
If an error occurs and a stack-trace is present, OXIDE will (in most circumstances) include a deep link to the source of the error.
This not only works for core application code, but also works for 'App packages' and 'App libraries' (TS apps).
If you are making use of unit testing inside App packages, you can view the test reports. OXIDE respects ANSI color output and also has support for emojis. This results in expressive and rich-formatted report output:
