AoT: inheritance error not reported correctly

I’m submitting a … (check one with “x”)

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior If a component extends a class with implemented lifecycle hooks, they’re not being called when building with aot (both in prod and dev). It’s alright though when running ng build --prod --aot=false

Expected behavior Lifecycle hooks inheritance should be working

Minimal reproduction of the problem with instructions

import { Component, OnInit } from '@angular/core';

class Foo implements OnInit {
    ngOnInit() {
        alert('Foo initialized');
    }
}

@Component({
    selector: 'app-root',
    template: 'App works',
})
export class AppComponent extends Foo {}

What is the motivation / use case for changing the behavior?

Please tell us about your environment: Windows 10

• Angular version: 4.0.3

• Browser: any

• Language: TypeScript 2.3.0

• Node (for AoT issues): node --version = 7.8.0

[chuckjaz]

The is an error condition that is not being reported ngc nor by TypeScript as, by default, the "declaration" option is false.

An exported class must only extend exported classes. To have TypeScript report this case, change the "declaration" option to true in your tsconfig.json file.

To fix this in your code, add export in front of the declaration of Foo.

I am keeping this open as a bug because we should report this as an error in ngc even if TypeScript allows it.

REPO:

1. git clone https://github.com/chuckjaz/e16335.git
2. cd e16335
3. yarn
4. ng build --aot

Expected: Error report that Foo is not exported. Received: Compiled successfully but produced incorrect code (“App works: not initialized” instead of “App works: initialized”).

[angular-automatic-lock-bot[bot]]

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}