title: Lazy loading after page reload cannot find some module declarations
body: <p>My app consists of </p>
  
  <ul>
  <li>Route /home -> app module </li>
  <li>Route /dashboard -> Dashboard module </li>
  <li>Route /profile -> profile module </li>
  <li>Route /event -> event module </li>
  <li>Route /services -> services module </li>
  </ul>
  
  <p>I am using lazy loading and all works well </p>
  
  <p>All navigation combinations after a page reload work well. Not matter from where to where. </p>
  
  <p>Eg: </p>
  
  <p>Profile -> Dashboard 
  Services -> Dashboard 
  Home -> Dashboard 
  etc </p>
  
  <p>But only after a page reload one navigation does not work: </p>
  
  <p>event -> Dashboard doesn't work only! All other routing after page reload works ! </p>
  
  <p>I get errors of </p>
  
  <pre><code>breadcrumbs.js:64 ERROR Error: Template error: Can't bind to 'data' since it isn't a known property of 'app-timeline-chart'.
  </code></pre>
  
  <p>Here is my code: </p>
  
  <p>appModule</p>
  
  <pre><code>
  declare function require(moduleName: string): any;
  
  const {version: appVersion} = require('../../package.json');
  
  Sentry.init({
    dsn: 'https://e6aa6074f13d49c299f8c81bf162d88c@sentry.io/1194244',
    environment: environment.production ? 'Production' : 'Development',
    release: appVersion,
  });
  
  
  @Injectable()
  export class SentryErrorHandler implements ErrorHandler {
    constructor() {
    }
  
    handleError(error) {
      // Sentry.showReportDialog({ eventId });
      // const eventId = Sentry.captureException(error.originalError || error);
      console.log(error);
      Sentry.captureException(error)
    }
  }
  
  
  @NgModule({
    imports: [
      SharedModule,
      BrowserModule,
      BrowserAnimationsModule,
      AppRoutingModule,
      HttpClientModule,
      AngularFireModule.initializeApp(environment.firebase),
      AngularFirestoreModule,
      AngularFirestoreModule.enablePersistence({synchronizeTabs: true}),
      AngularFireFunctionsModule,
      AngularFireStorageModule,
      AngularFireAuthModule,
      AngularFirePerformanceModule,
      MaterialModule,
    ],
    declarations: [
      AppComponent,
      SideNavComponent,
      HomeComponent,
      EventFormComponent,
      ActivityFormComponent,
    ],
    entryComponents: [
      EventFormComponent,
      ActivityFormComponent,
    ],
    providers: [
      // {provide: ErrorHandler, useClass: SentryErrorHandler}
      {provide: ErrorHandler, useClass: environment.production ? SentryErrorHandler : ErrorHandler},
      {provide: MatPaginatorIntl, useClass: MatPaginatorIntlFireStore},
      {provide: FunctionsRegionToken, useValue: 'europe-west2'}
    ],
    bootstrap: [AppComponent],
  })
  
  export class AppModule {
  }
  
  </code></pre>
  
  <p>And the dashboardModule </p>
  
  <pre><code>@NgModule({
    imports: [
      CommonModule,
      SharedModule,
      MaterialModule,
      DashboardRoutingModule
    ],
    exports: [
    ],
    declarations: [
      DashboardComponent,
      UploadComponent,
      UploadInfoComponent,
      ChartsPieComponent,
      ChartsXYComponent,
      ChartsTimelineComponent,
      SummariesComponent,
      ChartActionsComponent,
      EventSearchComponent,
      EventsExportFormComponent,
      EditInputComponent,
      UploadErrorComponent,
      ActivityMetadataComponent,
      EventTableComponent,
    ],
    entryComponents: [
      UploadErrorComponent,
      EventsExportFormComponent,
    ],
    providers: [
    ]
  })
  
  
  
  export class DashboardModule { }
  </code></pre>
  
  <p>As you saw on the error the specific component <code>ChartsTimelineComponent,</code>  used that it errors on not finding it, if I move it to a shared component does not fail. </p>
  
  <p>However, that is silly because only dashboard component uses it, and if there was no page reload or navigation from another module all works fine. </p>
  
  <p>Any clue? </p>
  
  <p>I know its very hard what I am asking , it might be even an angular bug but I am mainly searching for any clues , or where to turn my neck to. </p>
  
  <p>After some investigation the question is more about </p>
  
  <p>App.module 
  ChildA.module 
  ChildB.module </p>
  
  <p>ChildA and ChildB have components that base on the same abstract class meaning that they both eg have</p>
  
  <p>ComponentForChildA, ComponentForChildB and they base on ComponentAbstractClass </p>