ref: Expose Raven's constructor publicly. Kinda.

[kamilogorek]

Resolves: #1269

[MaxBittker]

would it be worth prefixing this with _ to act as more warning? The comment is good but the name isn't "scary" on it's own like "dangerouslysetinnerhtml" or something

[kamilogorek]

@MaxBittker I wanted it to be in line with node's implementation for now. It'll be updated and taken care of correctly in v4 :)

[zivl]

@kamilogorek thanks for the super-fast delivery!
Cheers!

[dan-kez]

Quick question on this documentation @kamilogorek

Rather than

someAppReporter('__DSN__', {
  ...config goes here
});

shouldn't it be:

someAppReporter.config('__DSN__', {
  ...config goes here
}).install();

[kamilogorek]

@dmk255 ah! Yes, thank you. I forgot the config. Although it shouldn't use install as it'd then literally install all the error/promise handlers. We want to avoid it in this scenario, as multiple reporters are meant to be used manually via captureException and captureMessage.

Updated: f3b3500

[dan-kez]

@kamilogorek Quick follow up on that though. I haven't had that issue in my local testing with multiple install calls. That said, I am using webpack code chunking and only call install in separate chunks. This so far has allowed me to have multiple sentry reporting pipelines for chunked pages that each have their own redux stores.

Is there is a subtly that I'm missing or am I fine so long as I ensure that install is called from separate files (chunks)?

[kamilogorek]

What install does is add all the handlers to the current page - https://github.com/getsentry/raven-js/blob/master/src/raven.js#L239-L266
What that implies, is that when you call install twice, you'll get multiple handlers and errors will be caught by both of them. Unless the previous one will be removed, which can be done using uninstall OR page will be reloaded and all the handers wiped out.

Everything I said is true only when you actually rely on handlers and don't just use capture methods yourself, as those are created per-instance.