Skip to main content

Configuration File Reference

The DHIS2 application platform configuration file is d2.config.js.
It should be placed in the root directory of your project, next to package.json

The default export from d2.config.js should be a JSON-srializable object.

All properties are technically optional, but it is recommended to set them explicitly.

Supported Properties

The following configuration properties are supported:

typestringappEither app or lib
namestringpkg.nameA short, machine-readable unique name for this app
titlestringconfig.nameThe human-readable application title, which will appear in the HeaderBar
direction'ltr', 'rtl', or 'auto''ltr'Sets the dir HTML attribute on the document of the app. If set to 'auto', the direction will be inferred from the current user's UI locale setting. The header bar will always be considered 'auto' and is unaffected by this setting.
idstringThe ID of the app on the App Hub. Used when publishing the app to the App Hub with d2 app scripts publish. See this guide to learn how to set up continuous delivery.
descriptionstringpkg.descriptionA full-length description of the application
authorstring or objectpkg.authorThe name of the developer to include in the DHIS2 manifest, following package.json author field syntax.
entryPoints.appstring./src/AppThe path to the application entrypoint (not used for libraries)
entryPoints.pluginstringThe path to the application's plugin entrypoint (not used for libraries)
entryPoints.libstring or object./src/indexThe path to the library entrypoint(s) (not used for applications). Supports conditional exports
dataStoreNamespacestringThe DataStore and UserDataStore namespace to reserve for this application. The reserved namespace must be suitably unique, as other apps will fail to install if they attempt to reserve the same namespace - see the webapp manifest docs
customAuthoritiesArray(string)An array of custom authorities to create when installing the app, these do not provide security protections in the DHIS2 REST API but can be assigned to user roles and used to modify the interface displayed to a user - see the webapp manifest docs
minDHIS2VersionstringThe minimum DHIS2 version the App supports (eg. '2.35'). Required when uploading an app to the App Hub. The app's major version in the app's package.json needs to be increased when changing this property.
maxDHIS2VersionstringThe maximum DHIS2 version the App supports.
coreAppbooleanfalseADVANCED If true, build an app artifact to be included as a root-level core application
standalonebooleanfalseADVANCED If true, do NOT include a static BaseURL in the production app artifact. This includes the Server field in the login dialog, which is usually hidden and pre-configured in production.
pwaobjectADVANCED Opts into and configures PWA settings for this app. Read more about the options in the PWA docs.

Note: Dynamic defaults above may reference pkg (a property of the local package.json file) or config (another property within d2.config.js).


const config = {
name: 'my-app',
title: 'My Application',
description: 'A simple application for doing DHIS2 things',

type: 'app',

entryPoints: {
app: './src/App',

dataStoreNamespace: 'my-custom-app-namespace',
customAuthorities: ['my-app-analytics-user'],

module.exports = config

Setting the DHIS2 version

The minDHIS2Version and maxDHIS2Version allow specifying which DHIS2 version the app is compatible with. This can be used to have multiple versions of the app on the App Hub, each with their own range of supported DHIS2 versions.

For example, let's say you want to adjust your app to a breaking change in the DHIS2 api. Let's assume that the code on your app's default branch (main) has not yet been adapted to the breaking change and that you're working with DHIS2's workflows:

  1. Set the maxDHIS2Version in d2.config.js to the last DHIS2 version that's still compatible with the code on main.
  2. Branch main to a maintenance branch. The recommended naming pattern is N.x, where N should be replaced with the app's current major version (i.e. 100.x, 101.x, etc.). See also semantic-release's documentation on branches. The app's version can be found in package.json, look for the version field.
  3. On main update the minDHIS2Version to the first DHIS2 version that contains the breaking change. It's important to publish the minDHIS2Version change as a breaking change. An easy way to do that is to include the BREAKING CHANGE label in the commit that changes the minDHIS2Version (see the semantic-release documentation on their commit conventions).