Warning: Experimental

(sudo) npm install -g bugger

Debug runner for nodejs modules: bugger examples/simple.js

Load coffee-script modules: bugger examples/http_network.coffee

Pass parameters: bugger examples/server.js -- --port=3000

The correct URL will be written to the output. It should look similar to this:

chrome-devtools:https://devtools/bundled/devtools.html?ws=127.0.0.1:8058/websocket

• -h, --help, -v, --version do what you'd expect them to do
• --no-brk prevents a breakpoint to be added on the first line of the script
• --webhost, --webport specifiy where the webserver with inspector will be listening

• Step-by-step debugging
• SourceMaps for coffee-script
• Variable introspection
• stdout of the process is forwarded to console.log
• Evalute expressions in the console
• Monitor outgoing http(s) requests your script does (Network tab)
• Heap snapshots and CPU profiles (Profiles tab)
• Use console.{time, timeEnd, timeStamp}, network request and heap usage reporting (Timeline tab)
• Live edit the running JavaScript code (not in 0.5.x)

• Better usage of the Events/Timeline section
• Decision whether the "Resources"-tab makes any sense
• Support for cluster/fork - maybe consider those kind-of (web) workers..?

• require doesn't work in the console, it maybe should be more repl-like
• LiveEdit is only working for the compiled javascripts, not for the source mapped files. This appears to be a limitation of the WebKit developer tools.

bugger was heavily inspired by node-inspector and nodebug. Unfortunately both those projects are pretty outdated and also I was on vacation and had way too much time.

bugger uses the Chrome developer tools as it's frontend.

• https://svn.webkit.org/repository/webkit/trunk/Source/WebCore/inspector
• https://developers.google.com/chrome-developer-tools/docs/protocol/1.0
• https://code.google.com/p/v8/wiki/DebuggerProtocol