Modern UI Troubleshooting: Build Options
For troubleshooting errors during building of the Modern UI, you can use additional build options, which are described in the following sections.
Log Level for Building the Source Code
You can specify the log level in the build command, as shown in the following example. The log level determines the minimum threshold at which a logging method should be enabled.
npm run build-dev -- --env LOG_LEVEL=trace
The following log levels are available:
- fatal
- error
- warn
- info
- debug
- trace
For more details on log levels, see documentation of the pino logger.
When the build is completed, the links to the log files are displayed along with the result of the build.
Building of the Source Code for a Particular Tenant
As described in Customization Project with UI Changes: How UI Customization Works, the source code for published changes to the Modern UI in a particular tenant is located in the FrontendSources\screen\src\Screens_Customization\<Tenant Name>\screens folder. For troubleshooting errors during building of the Modern UI changes of a particular tenant of your instance, you can run the following command in the FrontendSources folder, where TenantName is the tenant name in the Login Name box of the Tenants (SM203520) form.
npm run build-dev -- --env tenant=TenantName
You can use the tenant=TenantName
parameter with any other parameters,
such as screenIds
or modules
, or with the
watch
command with parameters. For details about the parameters, see
Modern UI Development: Building of the Source Code.
npm run build
command
(instead of npm run build-dev
) during publication of a customization
project with the Modern UI
changes. You can adjust this behavior by adding the respective keys in the
Web.config file. For details about the keys, see Customization Project with UI Changes: General Information.