Platform settings file

This article covers various properties that can be configured in the Microsoft Dynamics 365 Commerce platform settings file.

The platform.settings.json file under the \src\settings\ directory holds various platform property settings that are used by the Commerce e-commerce runtime. This file might not exist by default. If it doesn't exist, you can add it under the \src\settings\ directory. The following example of a platform.settings.json file shows various supported property settings.

    "dataActionTimeoutInMs": 4000,
    "minClientChunkSize": 30000,
    "excludeModules": [ ],
    "namespaceExtensions" : [ ],
    "secretsManagerOUN" : 128



The dataActionTimeoutInMs property defines the maximum amount of time, in milliseconds, that data actions will wait for a response before they time out. The time-out represents a lower bound for page response, because the action framework will wait as long as the defined time-out before it times out and returns the page. The default value is 4,000 milliseconds (4 seconds).


The minClientChunkSize property defines the minimum size, in bytes, of webpack JavaScript chunks that will be sent to the browser. JavaScript chunks that are smaller than the minimum size will be grouped together to form chunks that are larger than the minimum size. The smaller the minimum size is, the more chunks will be generated. In this case, more code splitting will occur, and less unused JavaScript code will be included. However, many smaller chunks must be downloaded. By contrast, the larger the minimum size is, the fewer overall chunks will be generated. In this case, fewer JavaScript files must be downloaded, but some unused JavaScript code might be included. The default value is 30,000 bytes (30 KB).


The excludedModules property defines a set of modules that will be excluded from webpack JavaScript chunks. Commerce modules are bundled into JavaScript chunks and sent to the browser on the client side. However, if modules aren't required on a site, they can be excluded to help reduce the size of JavaScript chunks and help increase the speed of page loads.


The namespaceExtensions property defines the supported namespaces that are used for module registration. By default, the only supported namespace is @msdyn365-commerce-modules. This namespace contains all the module library modules and the core set of modules. The module package name is defined in the following format: <namespace>/<module_name>. If modules are published that use a new namespace, the namespace can be added to the settings.


The secretsManagerOUN property specifies the operating unit number to use when retrieving secret values using the secret manager class. This operating unit number should match that of the store that was used in Commerce headquarters to configure key vault parameters for Retail Server. For more information, see Set up Azure Key Vault for secure key management.

JavaScript bundling options

The Dynamics 365 Commerce framework generates JavaScript bundles by using a webpack-optimized configuration. Although the default configuration offers better "tree shaking" (removal of unused or dead code) and JavaScript chunking, the generation logic can be tuned further to help improve bundle generation. For better control of JavaScript bundling, the framework offers the following options.


The Commerce framework supports generating JavaScript bundles per module and loading only the bundles that are needed on a page. The enableModuleEntryPoints platform setting enables the generation of JavaScript bundles per module.

Less JavaScript means better page performance and less unused JavaScript on a site page. However, this bundling can cause an increase in the number of JavaScript requests, depending on the number of modules that are used on the page. Therefore, we recommend that you carefully analyze the results in your development environment before you enable this platform setting in production.

To generate JavaScript bundles per module, add the following platform setting in the platform.settings.json file.

"enableModuleEntryPoints": true


For complex applications that have more modules and/or more customization, the build platform setting can cause the webpack to use more memory. In these cases, the default node heap memory size won't be sufficient and can cause heap "out of memory" errors. To increase the heap memory, update the build target in the package.json file by setting NODE_OPTIONS to increase the heap memory limit, as shown in the following example.

"build": "SET NODE_OPTIONS=--max_old_space_size=4096 && ..."


Smaller JavaScript bundles put less pressure on the main thread by causing the browser to process and run the script faster. Therefore, there is a direct correlation between the size of bundles and the total blocking time performance. The maxClientChunkSize platform setting helps control the bundle size by splitting the larger JavaScript bundles into multiple parts, as shown in the following example.

"maxClientChunkSize": 500000 // 500KB unzipped size

Additional resources

Request properties object

App settings

Extend a module definition file

Cookie API overview

Interactive components overview

Mock the signed-in state during local development

Globalize modules by using the CultureInfoFormatter class

Set up Azure Key Vault for secure key management