Throwing error in Angular2 ngOnInit does not work as expected

Asked Jul 10 '17 at 12:18

Active Oct 11 '17 at 07:43

Viewed 925 times

When I have an error happen inside ngOnInit() that error seems to be bubbled up with an TypeError: this._unregisterListenersFn is not a function error instead.

Example:

constructor() {
   throw Error('error in constructor');
}

gives expected result in console window. but in ngOnInit():

ngOnInit() {
   throw Error('error in ngOnInit')
}

gives first 'error in ngOnInit' as expected, but also

TypeError: this._unregisterListenersFn is not a function

I'm trying to handle all errors with an custom error handler, but when an error happens inside ngOnInit() I only get the latest error, and not the error causing the errors in the first place.

Edit-follow-up: I think I've found the root cause in NgbPopover. The error Message shown in Chrome Developer Tools is:

TypeError: this._unregisterListenersFn is not a function
    at NgbPopover.webpackJsonp.../../../../@ng-bootstrap/ng-bootstrap/popover/popover.js.NgbPopover.ngOnDestroy (popover.js:128)

edited Oct 11 '17 at 07:43

asked Jul 10 '17 at 12:18

jonas

1,592
3
20
29

Do you get this in dev env? – Bogdan Bogdanov Jul 10 '17 at 12:27
I'm getting this behavior in both dev and prod environement. – jonas Jul 10 '17 at 12:40
1

Is there any listeners that you are trying to reach before ngOnInit because I started one angular 2 application with reproducing your scenario and it gives me the expected error. – Bogdan Bogdanov Jul 10 '17 at 12:55
Thank you for taking your time! Thanks to you I've traced the issue down to ng-bootstrap/ngbPopover that threw another error overriding my first error >. – jonas Jul 10 '17 at 13:39
You are welcome! – Bogdan Bogdanov Jul 10 '17 at 17:41

Throwing error in Angular2 ngOnInit does not work as expected

0 Answers0