A Node.js module for inspecting, profiling and debugging Node.js applications through a web browser


A Node.js module for inspecting and debugging Node.js applications through a web browser

NodeMonkey runs a simple server and uses Socket.IO to create a websocket connection between the browser and server. It captures anything that would normally be logged to the terminal, converts it to JSON and passes it to the browser where it is then logged to the console for inspection.

Version 0.2.0 also introduces code profiling functionality and the ability to send commands to your Node.js application from your web browser.
Version 0.2.1 introduces major changes and cleanup. You can now register your own commands that can be run from the browser's Javascript console.


The motivation for this project came from trying to debug a Node.js server I wrote that used websockets. I found it problematic trying to inspect objects with the terminal. I tried using the built-in debugging that works with the Chrome Developer Tools plugin for Eclipse. Unfortunately, I ran into a problem where setting breakpoints to inspect objects would cause the server to stop responding to heartbeats thus causing the client to disconnect. This would entirely mess up my debugging efforts. All I really needed to do was have a good way to inspect objects. I searched Google and found projects like node-inspector, which doesn't work with the latest versions of Node, and node-codein which has many bugs. And neither works with Firefox.

So NodeMonkey was born!

Any browser with a Javasript console and websocket support!

npm install node-monkey

NodeMonkey is primarily designed for debugging and for now should only be used for such. I haven't implemented any sort of authorization to prevent anyone from gaining access to the data that is dumped out. If you are concerned about other's potentially gaining access while you are debugging, you should change the host from to something more secure like Definitely don't include it in production code before authorization is in place, and even then it's debatable whether there's a good reason.

To get a quick start see the limited examples below. For complete documentation see the following links:

Using NodeMonkey is extremely easy. All you have to do is include the following line in your Node.js application. Anything that is logged to the console after this will show up in the browser console once connected. It captures all output to console.log(), console.warn() and console.error().

var nomo = require('node-monkey').start([options]);

To connect your browser simply go to in your web browser. If you change the default host and port bindings be sure to adjust your URL accordingly.

As an alternative to viewing output through this page, you can also view output in the console of your own web application by including the following lines (adjust the host and port as necessary, this is based on the defaults):

<script type="text/javascript" src=""></script>
<script type="text/javascript" src=""></script>
<script type="text/javascript" src=""></script>
<script type="text/javascript" src=""></script>

NOTE: You do NOT have to refresh the page when you restart your Node.js application to continue to receive output. Socket.IO will automatically reconnect.

  • host: The host network interface to bind to. Default is which means ALL interfaces.
  • port: The port to listen on. Default is 50500.
  • overrideConsole: Set this to false to prevent NodeMonkey from overriding the console functions when you start it. You can call nomo.replaceConsole() any time to override the console functions and nomo.revertConsole() to change it back. Default is true.
  • suppressOutput: Use this to suppress terminal output when console.log() is called, freeing the console from clutter and allowing you to only inspect objects through the browser. Default is true.
  • saveOutput: If data is logged before you are able to connect your browser, you may still want to be able to view this data. Setting this option to true causes node-monkey to save the output and dump it out to the browser once you connect. Default is true. NOTE This will not be effective in newer versions of Firefox that have a proper built-in dev console.
  • clientMaxBuffer: The maximum number of messages to buffer while waiting for the console to open. Only has an effect if saveOutput is enabled. Default is 50.
  • silent: If true then nothing will be logged to the console when started. Default is false.
  • convertStyles: Whether to convert style related terminal escape sequences to corresponding JS console styles. Default is true.