npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

blunder-js

v0.4.0

Published

Notify Blunder on JavaScript exceptions

Downloads

22

Readme

Blunder-JS

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

Installation

Using npm:

npm install blunder-js

Setup

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're using Node.js you might need to install the request library too, on which Blunder depends:

npm install request

Basic Usage

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

var blunder = new blunderJs.Client({projectId: 1, projectKey: 'abc', component: 'frontend'});

Or if you are using browserify/webpack/etc:

var BlunderClient = require('blunder-js');
var blunder = new BlunderClient({projectId: 1, projectKey: 'abc', component: 'frontend'});

Then you can send a textual message to Blunder:

var promise = blunder.notify(`user id=${user_id} not found`);
promise.then(function(notice) {
  console.log('notice id', notice.id);
});
promise.catch(function(err) {
  console.log('blunder error', err);
});

Or report catched errors directly:

try {
  // This will throw if the document has no head tag
  document.head.insertBefore(document.createElement('style'));
} catch(err) {
  blunder.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 = blunder.wrap(startApp);

// Any exceptions thrown in startApp will be reported to Blunder.
startApp();

or use call shortcut:

var startApp = function() {
  // This will throw if the document has no head tag.
  document.head.insertBefore(document.createElement('style'));
}

blunder.call(startApp);

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 {
  startApp();
} catch (err) {
  blunder.notify({
    error:       err,
    context:     { component: 'bootstrap' },
    environment: { env1: 'value' },
    params:      { param1: 'value' },
    session:     { session1: 'value' },
  });
  throw err;
}

Severity

Severity allows categorizing how severe an error is. By default, it's set to error. To redefine severity, simply overwrite context/severity of a notice object. For example:

blunder.notify({
  error: err,
  context: { severity: 'warning' }
});

User information

To send user information to Blunder, either create a filter or use setUser(userId: string, userEmail: string, userName: string) on an instance of the BlunderClient. You can also use setUserId(id: string), setUserEmail(email: string) or setUserName(name: string) on a client instance if you only have, or only care about one of the bits.

Since Blunder mostly works with .NET and their way of doing things, the backend will prefer grouping on UserName instead of the others. If you only set one piece of user info, make it UserName.

Filtering errors

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

The Blunder 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 Blunder, 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:

blunder.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:

blunder.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, blunder.min.js has the following line:

//# sourceMappingURL=blunder.min.js.map

Please note that the Blunder 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.

blunder.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;
});

Custom reporters

If you're interested in inspecting the information reported to Blunder 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>
  blunder.addReporter(function(notice) {
    console.log(notice);
  });
</script>

Unwrapping console

blunder-js automatically wraps console.log function calls in order to collect logs and send them with first error. You can undo it using following code:

if (env === 'development') {
    let methods = ['debug', 'log', 'info', 'warn', 'error'];
    for (let m of methods) {
        if (m in console && console[m].inner) {
            console[m] = console[m].inner;
        }
    }
}

Integration

window.onerror

blunder-js automatically setups window.onerror handler when script is loaded. It also makes sure to call old error handler if there are any. Errors reported by window.onerror can be ignored using ignoreWindowError option:

var blunder = new blunderJs.Client({ignoreWindowError: true});

What does "Script error" mean?

See https://developer.mozilla.org/en/docs/Web/API/GlobalEventHandlers/onerror#Notes.

Contributing

Install dependencies:

npm install

Build project:

webpack

License

Copyright for portions of project are held by Airbrake Technologies, Inc, 2017 as part of project Airbrake. All other copyright for project Blunder are held by Per Christian B. Viken, 2017. It is free software, and may be redistributed under the terms specified in the LICENSE file.