Indicates is bundled by AdminJS files like:

• components.bundle.js
• global.bundle.js
• design-system.bundle.js
• app.bundle.js should be taken from the same server as other AdminJS routes (default) or should be taken from an external CDN.

If set - bundles will go from given CDN if unset - from the same server.

When you can use this option? So let's say you want to deploy the app on serverless environment like Firebase Cloud Functions. In that case you don't want to serve static files with the same app because your function will be invoked every time frontend asks for static assets.

Solution would be to:

• create public folder in your app
• generate bundle.js file to .adminjs/ folder by using AdminJS#initialize function (with process.env.NODE_ENV set to 'production').
• copy the before mentioned file to public folder and rename it to components.bundle.js
• copy './node_modules/adminjs/lib/frontend/assets/scripts/app-bundle.production.js' to './public/app.bundle.js',
• copy './node_modules/adminjs/lib/frontend/assets/scripts/global-bundle.production.js' to './public/global.bundle.js'

• • copy './node_modules/adminjs/node_modules/@adminjs/design-system/bundle.production.js' to './public/design-system.bundle.js'

• host entire public folder under some domain (if you use firebase - you can host them with firebase hosting)
• point AdminJS.assetsCDN to this domain

Environmental variables passed to the frontend.

So let say you want to pass some GOOGLE_MAP_API_TOKEN to the frontend. You can do this by adding it here:

new AdminJS({env: {
  GOOGLE_MAP_API_TOKEN: 'my-token',
}})

and this token will be available on the frontend by using:

AdminJS.env.GOOGLE_MAP_API_TOKEN

Translation file. Change it in order to:

• localize admin panel
• change any arbitrary text in the UI

This is the example for changing name of a couple of resources along with some properties to Polish

{
  ...
  locale: {
    language: 'pl',
    translations: {
      labels: {
        Comments: 'Komentarze',
      }
      resources: {
        Comments: {
          properties: {
            name: 'Nazwa Komentarza',
            content: 'Zawartość',
          }
        }
      }
    }
  }
}

As I mentioned you can use this technic to change any text even in english. So to change button label for a "new action" from default "Create new" to "Create new Comment" only for Comment resource you can do:

{
  ...
  locale: {
    translations: {
      resources: {
        Comments: {
          actions: {
            new: 'Create new Comment',
          }
        }
      }
    }
  }
}

Check out the i18n tutorial to see how internationalization in AdminJS works.

Branding Options

You can use them to change how AdminJS looks. For instance to change name and colors (dark theme) run:

new AdminJS({
  branding: {
    companyName: 'John Doe Family Business',
    theme,
  }
})

Contains all the translations for given language. Everything is divided to

sections/blocks like actions, properties, buttons, labels and messages, but also the same sections can can be nested under 'resources' property.

This allows you to define translations either for entire UI or for a specific resource. Take a look at this example:

{
  translations: {
    buttons: {
      save: 'Save it',
    },
    resources: {
      Comments: {
        buttons: {
          save: 'Save this comment'
        }
      }
    }
  }
}

In the example above all save buttons will be named: 'Save it'. All but save button in Comments resource. Where the button name will be: Save this comment.