Maximum call stack size exceeded with @bugsnag/plugin-angular in SSR

Following #441, I’m now getting RangeError: Maximum call stack size exceeded during server-side rendering in Angular.

{
  "@bugsnag/js": "^5.1.0",
  "@bugsnag/plugin-angular": "^5.1.0"
}

// core.module.ts

import bugsnag from '@bugsnag/js';
import { BugsnagErrorHandler } from '@bugsnag/plugin-angular';

const bugsnagClient = bugsnag({ ... });

export function errorHandlerFactory() {
  return new BugsnagErrorHandler(bugsnagClient);
}

@NgModule({
  ...
  providers: [
    { provide: ErrorHandler, useFactory: errorHandlerFactory },
    ...
  ]
})
export class CoreModule {}

// core.server.module.ts

import { CoreModule } from '@core/core.module';

@NgModule({
  imports: [
    CoreModule,
    ...
  ]
})
export class CoreServerModule {}

If I’m not mistaken, since @bugsnag/js is universal, it doesn’t need to be initialised differently for server-side rendering, does it?

[axelboc]

Thanks @oleksmir, I did manage to update to @bugsnag/js on Node 10 without getting the error by initialising Bugsnag only in the browser. Not ideal since I have errors in SSR that are still not reported, but at least I’m up to date.

[bengourley]

I’ve been investigating this issue and cannot reproduce it. I used the project on this page: https://angular.io/guide/universal

Using node v10.15.1, here are the versions of the top-level dependencies that got installed:

angular-io-example@1.0.0 /Users/bengourley/Development/universal-angular
├── @angular-devkit/build-angular@0.11.4
├── @angular/animations@7.2.15
├── @angular/cli@7.3.9
├── @angular/common@7.2.15
├── @angular/compiler@7.2.15
├── @angular/compiler-cli@7.2.15
├── @angular/core@7.2.15
├── @angular/forms@7.2.15
├── @angular/http@7.2.15
├── @angular/platform-browser@7.2.15
├── @angular/platform-browser-dynamic@7.2.15
├── @angular/platform-server@7.2.15
├── @angular/router@7.2.15
├── @angular/upgrade@7.2.15
├── @bugsnag/js@6.2.0
├── @bugsnag/plugin-angular@6.2.0
├── @nguniversal/express-engine@7.1.1
├── @nguniversal/module-map-ngfactory-loader@7.1.1
├── @types/jasmine@2.8.16
├── @types/jasminewd2@2.0.6
├── @types/node@8.9.5
├── angular-in-memory-web-api@0.8.0 (github:brandonroberts/in-memory-web-api-bazel#50a34d84b627ec88816242dec77603d6dcb9c880)
├── core-js@2.6.5
├── jasmine-core@2.99.1
├── jasmine-spec-reporter@4.2.1
├── karma@3.0.0
├── karma-chrome-launcher@2.2.0
├── karma-coverage-istanbul-reporter@2.0.5
├── karma-jasmine@1.1.2
├── karma-jasmine-html-reporter@0.2.2
├── lodash@4.17.11
├── protractor@5.4.2
├── rxjs@6.5.2
├── ts-loader@4.5.0
├── ts-node@7.0.1
├── tslint@5.11.0
├── typescript@3.1.6
├── webpack-cli@3.3.2
└── zone.js@0.8.29

Error reporting works on the server and in the browser, and the node process not crash (unless I throw an error and make it).

Closing this off as it looks like this is no longer an issue. Please feel free to post steps to reproduce if you are still seeing an issue like this and believe Bugsnag to be the cause.