Closed marcominetti closed 10 years ago
:) I'm porting my application server from my js compiler/environment to node.js. One of the main feature is concurrent coding (just a little bit crazy) and I need to watch at console logs together with other mates...
Within my project, I have embedded only the console from your stack. So I can expose it through dedicated port (that I can expose through iptables on development/vpn subnet).
https://github.com/marcominetti/node-console
I'd really like you and other node-webkit-agent coders to join my project when it will be released, at least for your feedback!... :D
PS: are you planning to merge your agent to node-inspector one? Their one runs also during debugger breaks and @3y3 is doing excellent work with cpu/heap profiler (looking at his fork, I think he could be able to help also on https://github.com/c4milo/node-webkit-agent/issues/41). But your agent is much faster, more stable and maintainable (IMHO)... and works without debug flag. ;)
nice, I will be glad to look at your project once it is finished. As for merging node-webkit-agent to node-inspector, I haven't really thought about it. node-webkit-agent exists because I had a problem in production a needed to solve. So far, nobody has encourage me to merge it into node-inspector. Thanks for you PR!
I'm curious about the use case you had. Would you mind elaborating?