Compilation error Angular 7 and 8 in AoT

• I have read the README and API docs (if applicable); the issue is not covered there.
• I have searched the repository issues and pull requests; my query is not covered there.

---

• Expected behaviour: build success
• Actual behaviour: build failed
• Environment:
  • Node version: 8.12.0
  • Browser and browser version (if applicable): Chrome
• Steps to reproduce:

npm i
npm run build

ERROR in Error during template compile of ‘AppModule’ Function calls are not supported in decorators but ‘NgForageModule’ was called.

• Reproducible code sample:
  • stackblitz.com:

---

Additional information, screenshots etc go here.

[weronikasabiniewicz]

Hi everyone!

I have a problem with AOT compilation in Angular 7.1. I have tried config ngForage in both of presenting ways. The first was into it in AppModule constructor, and second one as a provider (with DEFULT_CONFIG). Unfortunately, when I use ngForage:

ngOnInit(){ this.forage.storeName = 'MyStorage; this.forage.setItem('key','value'); }

forage is NgForage as Dependency Injection in the constructor.

During the building isn’t any errors. Then, after load the website, I have a one error in the console:

This happened only if I have built it with aot option.

Do you know what I am doing wrong? Or is there any workaround?

[Alorel]

Yeah, I’ve gotten this bug too but I have no idea why after hours of debugging and trying out various solutions by people with similar issues. At the moment it appears to be a regression from Angular 6 as the module hasn’t changed (4.0.0 | 3.4.0).

If you have any solutions do let me know please!

You can get around it for now, though. NgForage consists only of services, so importing the module isn’t actually necessary; you can simply perform the default configuration in your AppModule’s constructor:

import {BrowserModule} from '@angular/core';
import {NgForageConfig} from 'ngforage';

@NgModule({imports: [BrowserModule]})
export class AppModule {
  public constructor(ngfConfig: NgForageConfig) {
    ngfConfig.configure(configurationOptions);
  }
}

Issue reported here: https://github.com/angular/angular/issues/23609#issuecomment-433450395