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
The notifier is built using a standalone browserify build and can be used with:
We include the full source code with the package, so you can use Browserify too.
If you prefer not to host the library yourself, airbrake-js is available on the excellent cdnjs CDN.
First you need to initialize notifier with project id and API key taken from Airbrake.io:
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
document.head.insertBefore(document.createElement("style"));
} catch(err) {
airbrake.notify(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.
document.head.insertBefore(document.createElement("style"));
}
startApp = airbrake.wrap(startApp);
// Any exceptions thrown in startApp will be reported to Airbrake.
startApp();
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 {
startApp();
} catch (err) {
airbrake.notify({
error: err,
context: { component: 'bootstrap' },
environment: { env1: 'value' },
params: { param1: 'value' },
session: { session1: 'value' },
});
throw err;
}
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 null value is returned, the notice is ignored.
- Otherwise 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 environment and application version:
airbrake.addFilter(function(notice) {
notice.context.environment = 'production';
notice.context.version = '1.2.3';
return notice;
});
In order to enable source map support you have to specify path to the source map file according to the source map specification. For example, airbrake.min.js has following line:
//# sourceMappingURL=airbrake.min.map
Please note that Airbrake backend downloads source map file in order to process backtrace. This means that 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 pattern and the values are URLs of your source maps.
airbrake.addFilter(function(notice) {
notice.context.sourceMaps = {
'*': 'https://domain.com/path/to/source.map', // for all files
'https://domain.com/path/to/file.min.js': 'https://domain.com/path/to/source.map'
};
return notice;
});
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.
<script>
airbrake.addReporter(function(notice) {
console.log(notice);
});
</script>
By default notifier setups window.onerror handler if onerror handler is not already setup. You can manually setup it using the following code:
var airbrake = new airbrakeJs.Client(...);
window.onerror = airbrake.onerror;
Integration with Angular is as simple as adding $exceptionHandler:
mod.factory('$exceptionHandler', function ($log, config) {
var airbrake = new airbrakeJs.Client({
projectId: config.airbrake.projectId,
projectKey: config.airbrake.key
});
airbrake.addFilter(function (notice) {
notice.context.environment = config.envName;
return notice;
});
return function (exception, cause) {
$log.error(exception);
airbrake.notify({error: exception, params: {angular_cause: cause}});
};
});
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);
}
See https://developer.mozilla.org/en/docs/Web/API/GlobalEventHandlers/onerror#Notes.
Install dependencies:
npm install
Run unit tests:
grunt test
Run integration tests:
grunt karma
Airbrake is maintained and funded by airbrake.io
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.