Hi! Inspired by a recentish issue on Github[1] I experimented a bit with the idea of having a Chrome Devtools Protocol implementation for nodejs that isn't built on top of the V8 debugger protocol.
The result is bugger 2[2]. It's still a bit rough around the edges and the test coverage is at around 0%. But some of the highlights: * Integrates into `chrome://inspect` * Supports `child_process#fork` for worker inspection * Fully featured repl with require in the console * Command Line API * The usual features known from node-inspector, like debugging via source panel, network traffic inspection, and profiling tools The whole thing is highly experimental and contains a fair amount of "placeholder code". But I thought I'd share it anyhow in case it ends up being useful to someone. Cheers, Jan [1] https://github.com/nodejs/node/issues/2546 [2] https://github.com/buggerjs/bugger#features -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/2c646249-4c6a-410c-a677-cd118ea01760%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
