node_debug, http based console/object explorer

[Connor Dunn]

Thought I'd show off this tool to be used with your node project. It
allows you to execute arbitrary commands through a HTTP interface, and
explore the results of the commands (if they are objects) in a tree
structure. It also allows you to asynchronously output to the console
(using debug.log(msg)).

Still quite rough around the edges but http://github.com/Connorhd/node_debug/tree/master
if you would like to have a look. http://i31.tinypic.com/2iicp39.png
for a screenshot.

Connor

[Felix Geisendörfer]

Very nice! So if I get this right, I could hook this into my existing
node app and explore it's state during runtime? Or is this just a
standalone tool?

-- Felix Geisendörfer aka the_undefined

On Sep 8, 11:24 pm, Connor Dunn <conno...@gmail.com> wrote:
> Thought I'd show off this tool to be used with your node project. It
> allows you to execute arbitrary commands through a HTTP interface, and
> explore the results of the commands (if they are objects) in a tree
> structure. It also allows you to asynchronously output to the console
> (using debug.log(msg)).
>

> Still quite rough around the edges buthttp://github.com/Connorhd/node_debug/tree/master
> if you would like to have a look.http://i31.tinypic.com/2iicp39.png
> for a screenshot.
>
> Connor

[ryan dahl]

2009/9/9 Felix Geisendörfer <fe...@debuggable.com>:

>
> Very nice! So if I get this right, I could hook this into my existing
> node app and explore it's state during runtime? Or is this just a
> standalone tool?
>

Yes - you just do

var debug = require("debug.js");
debug.listen(8080);

We'll be supporting more functionality later - like breakpoints.
(Everything that is available through the debugger protocol
http://code.google.com/p/v8/wiki/DebuggerProtocol) First we need to
have workers (the http server for the debugger needs to run in a
separate process because if a breakpoint is hit and it was in the same
process as your application, the server would stop too!)