A simple and flexible runtime config service for Angular application.
There are three steps to setup the config service using the default configuration file path of assets/config/config.json
.
- Install the
ng-config-service
package:npm install ng-config-service
- Create a configuration JSON file
assets/config/config.json
in your project. - Bootstrap the config service in the root module. Because the config service use the
HttpClient
to fetch the configuration data, please make sure thatHttpClientModule
is imported in the root module.
The last step uses a const bootConfigServiceProvider
that is exported from the ng-config-service
. This const is a APP_INITIALIZER
provider that uses a factory method to load configuration data during Angular bootstrap. The following code is an example using the default configuration file path.
import { BrowserModule } from '@angular/platform-browser'
import { NgModule } from '@angular/core'
import { HttpClientModule } from '@angular/common/http'
import { bootConfigServiceProvider } from 'ng-config-service'
@NgModule({
declarations: [AppComponent],
imports: [BrowserModule, HttpClientModule],
// use the APP_INITIALIZER to load configuration data
providers: [bootConfigServiceProvider],
bootstrap: [AppComponent],
})
export class AppModule {}
If you want to use a different URL of a configuration file path or an HTTP API, you only need to assign the URL to a pre-defined injection token NG_CONFIG_URL_TOKEN
in the above providers
metadata. The following is an example.
providers: [
{
provide: NG_CONFIG_URL_TOKEN,
useValue: 'path/to/my-config-file.json', // could be an URL API or an environment variable
},
bootConfigServiceProvider,
],
The config service can be injected and its public get<T>(key: string): T | undefined
method is used to get a configuration value. Following is a demo:
import { ConfigService } from 'ng-config-service'
@Component({
//...
})
export class MyComponent {
constructor(private configService: ConfigService) {}
myMethod() {
const aValue = this.configService.get('aKey')
}
}
If the config service fails to load the configuration data, due to either an invalid URL or wrong JSON syntax, it throws an Error exception that stops the Angular application bootstrap.
The Design Document and the Development Document describe the design consideration and the development details.
The project uses Angular CLI.
It should be compatible with Angular 6.0 or later.
The source code has two projects created by Angular CLI and uses its library support. It has a regular Angular application served as a demo project that uses the config service library. The config service source code is located in projects/ng-config-service
folder.
Because of the limitation of Angular CLI, both the package.json
and the project/ng-config-service/package.json
should use the name name
of ng-config-service
. For each new publish, update both package.json
files to use the same version
value.
In project root, build the library project using npm run build-lib
.
The demo app is build with the regular Angular CLI: ng build
. To run the demo, use ng serve --open
and you should see the property value configured in assets/config/config.json
file.
To create the NPM package, run npm run package
.
To publish the NPM package, run npm run publish
.
The cross-var
package is used to provide cross-platform portability.
We use SemVer for versioning. For the versions available, see the link to tags on this repository.
We use the demo app to test configuration service. Use ng test
to run the test.
It uses tslint-angular
and prettier
to enforce a consistent code format. The detail styles are defined in the tslint.json
file and the .prettierrc
file.
The project uses Compodoc to generate code documents. Just run npm run docs
to generate documents in the dist/documentation
folder.