Bitbucket is a code hosting site with unlimited public and private repositories. We're also free for small teams!



The node-reporter package is designed to assist you with responding to events that occur within your application, and providing some uniform process handling.

<a href="!/DamonOehlman/node-reporter"><img src="" alt="Build Status"></a>

Consider that you have a particular object that generates events, and those events might generate particular command-line output (as one example). While it is simple enough to wire up handlers to generate the appropriate output for a handler for the one object, if you have multiple objects that generate similar events then this becomes a tedious task. This is where reporter comes in.

Example Usage

The following shows a simple example of using the reporter. In this example, we create a simple EventEmitter that will emit events, and we use this to emit a click event.

Prior to this, though we setup a reporter and have it watch the target object and add a rule to handle the click case.

var events = require('events'),
    reporter = require('reporter'),
    target = new events.EventEmitter();

// make the reporter watch the target;

// add some rules to the reporter to handle click events
    click: function() {
        console.log('A click happened');

// tell the target to emit a click event


npm install reporter

Recent activity

Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.