No stacktrace and error details showed.

Hi everyone. I am using your Angular2 - raven-js integration but its appear do not work for me, no a really error is showed on sentry console.

Here is my NgModule config for Raven-js

Raven.config(PUBLIC DSN HERE ,
    {
        logger: 'javascript',
        environment: process.env.ENV,
        release: process.env.VERSION,
        ignoreErrors: [
            'ObjectUnsubscribedError',
            'WebSocket *',
            'WebSocket connection to *'
        ]
    }).install();
    Raven.setTagsContext({
        version: process.env.VERSION
    });

class RavenErrorHandler implements ErrorHandler {
  handleError(err:any) : void {
    Raven.captureException(err.originalError);
  }

providers: [{ provide: ErrorHandler, useClass: RavenErrorHandler }]

Also i uploaded my .js and .map files to sentry artifacts. I am using : https://github.com/AngularClass/angular2-webpack-starter and raven-js 3.7.0. if anyone can help, I appreciate it. Thanks !

[benvinegar]

error.originalException

@combmag – it should be err.originalError. The property name changed between Angular 2 release candidates

anyway , some errors do not show origin issue code,

@cesarlvielma – Do you have an example of such an error that I can use to test?

show me only vendor stack trace (Angular2 for this case) and not my .ts file where error is coded.

Not sure I follow. If you want the original stack trace, your build has to generate source maps and Sentry has to be able to locate them. See our source maps docs.

[QuentinFchx]

@benvinegar if I may, according to the angular ErrorHandler source code (https://github.com/angular/angular/blob/master/modules/@angular/core/src/error_handler.ts#L51) originalError might be undefined. If you just throw a random error, let’s say in a component’s constructor, the originalError prop will be empty. Why don’t we just send Raven the err passed as an argument?