By default, Raven makes a few efforts to try its best to capture meaningful stack traces, but browsers make it pretty difficult.

The easiest solution is to prevent an error from bubbling all of the way up the stack to window.

Reporting Errors Correctly

There are different methods to report errors and this all depends a little bit on circumstances.

try … catch

The simplest way, is to try and explicitly capture and report potentially problematic code with a try...catch block and Raven.captureException.

try {
} catch(e) {

Do not throw strings! Always throw an actual Error object. For example:

throw new Error('broken')  // good
throw 'broken'  // bad

It’s impossible to retrieve a stack trace from a string. If this happens, Raven transmits the error as a plain message.


Raven.context allows you to wrap any function to be immediately executed. Behind the scenes, Raven is just wrapping your code in a try...catch block to record the exception before re-throwing it.

Raven.context(function() {

Raven.wrap wraps a function in a similar way to Raven.context, but instead of executing the function, it returns another function. This is especially useful when passing around a callback.

var doIt = function() {
    // doing cool stuff

setTimeout(Raven.wrap(doIt), 1000)

Tracking Users

While a user is logged in, you can tell Sentry to associate errors with user data.

    email: '',
    id: '123'

If at any point, the user becomes unauthenticated, you can call Raven.setUserContext() with no arguments to remove their data. This would only really be useful in a large web app where the user logs in/out without a page reload.

This data is generally submitted with each error or message and allows you to figure out which users are affected by problems.

Capturing Messages


Passing Additional Data

The captureMessage, captureException, context, and wrap functions all allow passing additional data to be tagged onto the error.

The log level associated with this event. Default: error

Raven.captureMessage('Something happened', {
  level: 'info' // one of 'info', 'warning', or 'error'

The name of the logger used to record this event. Default: javascript

Raven.captureException(new Error('Oops!'), {
  logger: 'my.module'

Note that logger can also be set globally via Raven.config.

Tags to assign to the event.

  tags: {git_commit: 'c0deb10c4'}
}, function () { /* ... */ });

// NOTE: Raven.wrap and Raven.context accept options as first argument

You can also set tags globally to be merged in with future exceptions events via Raven.config, or Raven.setTagsContext:

Raven.setTagsContext({ key: "value" });

Tags given in setTagsContext are merged with the existing tags. If you need to remove a tag, use getContext to get the current context value, call setTagsContext with no parameters to remove all tags context data, and then call setTagsContext again with the tags that you want to keep.

const context = Raven.getContext(); // Note: Do not mutate context directly.
const tags = {...context.tags};
delete tags['TagNameToDelete'];
Raven.setTagsContext();             // Clear all current tags from the context.
Raven.setTagsContext(tags);         // Add back the tags you want to keep.

Be aware of maximum payload size - There are times, when you may want to send the whole application state as extra data. This can be quite a large object, which can easily weigh more than 200kB. This 200kB is currently the maximum payload size of a single event you can send to Sentry. When this happens, you'll get an HTTP Error 413 Payload Too Large message as the server response or (when keepalive: true is set as fetch parameter), the request will stay in the pending state forever (eg. in Chrome).

Arbitrary data to associate with the event.

  extra: {planet: {name: 'Earth'}}
}, function () { /* ... */ });

// NOTE: Raven.wrap and Raven.context accept options as first argument

You can also set extra data globally to be merged in with future events with setExtraContext:

Raven.setExtraContext({ foo: "bar" })

Data given in setExtraContext is merged with the existing extra data. If you need to remove a field from the extra context data, use getContext to get the current context value, call setExtraContext with no parameters to remove all extra context data, and then call setExtraContext again with the extra data content that you want to keep.

const context = Raven.getContext(); // Note: Do not mutate context directly.
const extra = {...context.extra};
delete extra['FieldKeyToDelete'];
Raven.setExtraContext();            // Clear all extra data from the context.
Raven.setExtraContext(extra);       // Add back the extra data that you want to keep.

Recording Breadcrumbs

Breadcrumbs are browser and application lifecycle events that are helpful in understanding the state of the application leading up to a crash.

By default, Raven.js instruments browser built-ins and DOM events to automatically collect a few useful breadcrumbs for you:

  • XMLHttpRequests
  • URL / address bar changes
  • UI clicks and keypress DOM events
  • console log statements
  • previous errors

You can also record your own breadcrumbs:

  message: 'Item added to shopping cart',
  category: 'action',
  data: {
     isbn: '978-1617290541',
     cartSize: '3'

To learn more about what types of data can be collected via breadcrumbs, see the breadcrumbs client API specification.

Note that you can also disable automatic breadcrumb collection entirely or disable specific collectors:

Raven.config('PUBLIC_DSN', {
  autoBreadcrumbs: {
    xhr: false

For more on configuring breadcrumbs, see Configuration.

Getting Back an Event ID

An event id is a globally unique id for the event that was just sent. This event id can be used to find the exact event from within Sentry.

This is often used to display for the user and report an error to customer service.


Raven.lastEventId() will be undefined until an event is sent. After an event is sent, it will contain the string id.


User Feedback

Often you might find yourself wanting to collect additional feedback from the user. Sentry supports this via an embeddable widget.

try {
} catch (err) {

For more details on this feature, see the User Feedback guide.

Verify Raven Setup

If you need to conditionally check if raven needs to be initialized or not, you can use the isSetup function. It will return true if Raven is already initialized:


Dealing with Minified Source Code

Raven and Sentry support Source Maps.

For more information, please read the Source Map docs. Also, checkout our Gruntfile for a good example of what we’re doing.

You can use Source Map Validator to help verify that things are correct.


If you’re hosting your scripts on another domain and things don’t get caught by Raven, it’s likely that the error will bubble up to window.onerror. If this happens, the error will report some ugly Script error and Raven will drop it on the floor since this is a useless error for everybody.

To help mitigate this, we can tell the browser that these scripts are safe and we’re allowing them to expose their errors to us.

In your <script> tag, specify the crossorigin attribute:

<script src="//" crossorigin="anonymous"></script>

And set an Access-Control-Allow-Origin HTTP header on that file.

Access-Control-Allow-Origin: *


By default, Raven.js capture unhandled promise rejections as described in official ECMAScript 6 standard.

Most Promise libraries however, have a global hook for capturing unhandled errors. You may want to disable default behaviour by setting captureUnhandledRejections option to false and manually hook into such event handler and call Raven.captureException or Raven.captureMessage directly.

For example, the RSVP.js library (used by Ember.js) allows you to bind an event handler to a global error event:

RSVP.on('error', function(reason) {

Bluebird and other promise libraries report unhandled rejections to a global DOM event, unhandledrejection. In this case, you don’t need to do anything, we’ve already got you covered by with default captureUnhandledRejections: true setting.

Please consult your promise library documentation on how to hook into its global unhandled rejection handler, if it exposes one.

Custom Grouping Behavior

In some cases you may see issues where Sentry groups multiple events together when they should be separate entities. In other cases, Sentry simply doesn’t group events together because they’re so sporadic that they never look the same.

Both of these problems can be addressed by specifying the fingerprint attribute.

For example, if you have HTTP 404 (page not found) errors, and you’d prefer they deduplicate by taking into account the URL:

Raven.captureException(ex, {fingerprint: ['{{ default }}', 'http://my-url/']});

For more information, see Customize Grouping with Fingerprints.

Preventing Abuse

By default, the Sentry server accepts errors from any host. This can lead to an abuse scenario where a malicious party triggers JavaScript errors from a different website that are accepted by your Sentry Project. To prevent this, it is recommended to whitelist known hosts where your JavaScript code is operating.

This setting can be found under the Project Settings page in Sentry. You’ll need to add each domain that you plan to report from into the Allowed Domains box. When an error is collected by Raven.js and transmitted to Sentry, Sentry will verify the Origin and/or Referer headers of the HTTP request to verify that it matches one of your allowed hosts.

You can edit this page on GitHub.