CoffeeScript TypeScript JavaScript HTML
Latest commit c0af7b7 Feb 23, 2017 @vmihailenco vmihailenco committed on GitHub Merge pull request #263 from airbrake/feature/clicks-history
Record clicks on DOM elements.

Airbrake-JS Build Status CDNJS

This is the JavaScript notifier for capturing errors in web browsers and reporting them to Airbrake.


Using npm:

npm install airbrake-js

or using Bower:

bower install airbrake-js-client


Example configurations can be found in examples, including:

The notifier is built using umd and therefore can be imported with AMD, CommonJS2 or as property in root.

If you prefer not to host the library yourself, airbrake-js is available on the excellent cdnjs.

Basic Usage

First you need to initialize the notifier with the project id and API key taken from

var airbrake = new airbrakeJs.Client({projectId: 1, projectKey: 'abc'});

Or if you are using browserify/webpack/etc:

var airbrakeJs = require('airbrake-js');
var airbrake = new airbrakeJs({projectId: 1, projectKey: 'abc'});

The simplest method is to report errors directly:

try {
  // This will throw if the document has no head tag
} catch(err) {
  throw err;

Alternatively, you can wrap any code which may throw errors using the client's wrap method:

var startApp = function() {
  // This will throw if the document has no head tag.
startApp = airbrake.wrap(startApp);

// Any exceptions thrown in startApp will be reported to Airbrake.

or use call shortcut:

var startApp = function() {
  // This will throw if the document has no head tag.

Advanced Usage

Notice Annotations

It's possible to annotate error notices with all sorts of useful information at the time they're captured by supplying it in the object being reported.

try {
} catch (err) {
    error:       err,
    context:     { component: 'bootstrap' },
    environment: { env1: 'value' },
    params:      { param1: 'value' },
    session:     { session1: 'value' },
  throw err;

Filtering errors

There may be some errors thrown in your application that you're not interested in sending to Airbrake, such as errors thrown by 3rd-party libraries, or by browser extensions run by your users.

The Airbrake notifier makes it simple to ignore this chaff while still processing legitimate errors. Add filters to the notifier by providing filter functions to addFilter.

addFilter accepts the entire error notice to be sent to Airbrake, and provides access to the context, environment, params, and session values submitted with the notice, as well as the single-element errors array with its backtrace element and associated backtrace lines.

The return value of the filter function determines whether or not the error notice will be submitted.

  • If a null value is returned, the notice is ignored.
  • Otherwise, the returned notice will be submitted.

An error notice must pass all provided filters to be submitted.

In the following example all errors triggered by admins will be ignored:

airbrake.addFilter(function(notice) {
  if (notice.sessions.admin) {
    // Ignore errors from admin sessions.
    return null;
  return notice;

Filters can be also used to modify notice payload, e.g. to set the environment and application version:

airbrake.addFilter(function(notice) {
  notice.context.environment = 'production';
  notice.context.version = '1.2.3';
  return notice;

Source map

In order to enable source map support you have to specify the path to the source map file according to the source map specification. For example, airbrake.min.js has the following line:


Please note that the Airbrake backend downloads the source map file to process the backtrace. This means that the source map should be publicly accessible via HTTP. So, for example, don't expect source map support to work on your local webserver running on localhost.

Custom source map URLs are supported by assigning a special property of notice.context called sourceMaps. The keys of the sourceMaps object represent shell filename patterns and the values are URLs of your source maps.

airbrake.addFilter(function(notice) {
  notice.context.sourceMaps = {
    '*': '', // for all files
    '': ''
  return notice;

Custom reporters

If you're interested in inspecting the information reported to Airbrake in your own code, you can register your own error reporter. Note that reporters added this way may be executed out-of-order.

In this example, reported errors are also logged to the console.

  airbrake.addReporter(function(notice) {



By default, the notifier sets up the window.onerror handler if the onerror handler is not already set up. You can manually set it up using the following code:

var airbrake = new airbrakeJs.Client(...);
window.onerror = airbrake.onerror;


You can catch and report exceptions thrown in jQuery event handlers and callbacks using the following code:

var airbrake = new airbrakeJs.Client(...);
if (window.jQuery) {
  airbrakeJs.instrumentation.jquery(airbrake, jQuery);

What does "Script error" mean?



Install dependencies:

npm install

Run unit tests:

karma start

Build project:



Airbrake is maintained and funded by

Thank you to all the contributors.

The names and logos for Airbrake are trademarks of Airbrake Technologies Inc.


Airbrake is Copyright © 2008-2015 Airbrake Technologies Inc. It is free software, and may be redistributed under the terms specified in the MIT-LICENSE file.