Loading Angular Configuration Before Your Angular App Starts

Nov 11, 2021 reading time 7 minutes

Loading Angular Configuration Before Your Angular App Starts

In this blogpost I want to describe two different ways how to load your settings before your Angular application starts. Although there already have been articles about this Tim Deschryver’s Blog Post ‘Build once deploy to multiple environments’ I want to point out two different ways of solving the issue as I see this as an reappearing issue in the Angular world.


The Problem

The problem comes with the approach of building your application once and deploying it everywhere, which means to all stages you are working with. Let this be DEV, STAGE and PROD for this case. What we NOT want to do is using the environment.stage.tsenvironment.prod.tsenvironment.<my-env>.ts files for building our application for each stage explicitly. That would mean that we have different builds on each environment and with this the issue that we might see errors on the stages which we have not seen on the stages before. This is why it is so important to build one artifact and deploy it everywhere.

But the different stages need different settings. On DEV, maybe I want to have a different log level than on STAGE or PROD. So how to achieve this when implementing the Angular app only once?

We have to find a mechanism which loads the settings and bootstraps then application afterward.



The APP_INITIALIZER from Angular provides the ability to load things before your app starts. Which might fill your needs in this case. Since the APP_INITIALIZER also supports Observables, it got even more handy and easier to use.

function initializeAppFactory(httpClient: HttpClient): () => Observable<any> {
  return () => httpClient.get("https://someUrl.com/api/settings").pipe(...);
  imports: [BrowserModule, HttpClientModule],
  declarations: [AppComponent],
  bootstrap: [AppComponent],
  providers: [
      provide: APP_INITIALIZER,
      useFactory: initializeAppFactory,
      deps: [HttpClient],
      multi: true,
export class AppModule {}

The problem with this approach is that when you have a module in the imports array which has a forRoot(...) method, and you want to pass some data into it which is loaded in the APP_INITIALIZER you have a chicken-egg-problem: The AppModule needs to gather all modules in the imports array, and therefore also runs the forRoot(...)s, if any, but the info to pass into the forRoot(...)s can only be gathered when the APP_INITIALIZER has been called. But to call this, the forRoot(...) has to have the info first, etc.

Using the fetch api

Let’s get a step back and see what we want to do. So before the complete app starts we want to ask for our data to have it present and the time angular kicks in and bootstraps. The place which bootstraps the app is the main.ts file.

import { enableProdMode } from '@angular/core';
import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';
import { environment } from '@environments/environment';
import { AppModule } from './app/app.module';
if (environment.production) {

Tim Deschryver’s Blog Post ‘Build once deploy to multiple environments’ describes the solution very well.

Angulars platformBrowserDynamic() takes an optional parameter called extraProviders?: StaticProvider[] which we can use to pass extra providers. In combination with the InjectionToken we can provide the config through an InjectionToken. We can use the Fetch api to load our data and when it is loaded, bootstrap our application and provide the config.

import { enableProdMode } from '@angular/core';
import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';
import { environment } from './environments/environment';
import { AppConfig, APP_CONFIG } from '...';
import { AppModule } from './app/app.module';
  .then((res) => res.json())
  .then((config) => {
    if (environment.production) {
    platformBrowserDynamic([{ provide: APP_CONFIG, useValue: config }])
      .catch((err) => console.error(err));

In your app you can provide the InjectionToken like

import { InjectionToken } from '@angular/core';
export const APP_CONFIG = new InjectionToken<AppConfig>('app.config');

After this you can inject the APP_CONFIG like

constructor(@Inject(APP_CONFIG) config: AppConfig) {
  // use your config

In your custom libraries, you do not need the forRoot() method for the data which gets resolved by the app start. You can provide the InjectionToken through a common library and then use the @Inject(APP_CONFIG) config: AppConfig wherever you need it.

Third Party Libs

As this runs good for your internal libraries you have control over, this may not work for third party libraries, which need a forRoot() with some data. In our security library we solved this with an StsConfigHttpLoader or loaders in general config-loader.ts which are used in an internal APP_INITIALIZER in the auth module. The loader either provides the data over http or gets it statically wrapped in a promise.

Another approach would be that you pass data at the start which can be replaced later, like default data to let the lib start and then replace it and provide it through a provider like described in my blogpost Configuring Angular libraries


Thanks to Tim Deschryver’s Blog Post Build once deploy to multiple environments for the inspiration to write this two (and a half) methods together.

Hope this helps