>
> 1) I am still not sure I understand how to integrate node-inspector with 
> my own Windows exe with embedded V8.  Is this where you would "attach" 
> using process._debugProcess(pid) ?  Currently my application does not use 
> node.js at all, so perhaps I need to get that working at a basic level 
> first?


To debug your Windows exe with embedded V8, you need to tell the embedded 
V8 to start listening for debugger connections. You are on the right track 
with `process._debugProcess(pid)`, that's the mechanism exposed by Node. 
Internally, Node is calling `v8::Debug::EnableAgent`, which is the API you 
want to call from your own Windows exe. See Node's EnableDebug[1] for more 
details.

It is up to you to decide what conditions/triggers will enable debugger in 
your application. Once the V8 debug agent is enabled, you can point Node 
Inspector the the port where the agent is listening on (by default 5858 in 
Node).
 

> 2) Among other reasons, we chose Typescript for its autocompletion and 
> static typing.  Are these features of Typescript supported, while 
> debugging, in Node Inspector?
>
Autocompletion and static typing are features used for *writing* code, I 
don't see why would you need them while *debugging* your code? The only use 
I can think of is live-edit of your code while debugging. As far as I know, 
autocompletion is not supported for other languages than javascript at the 
moment.

Talking about IDEs - JetBrain's WebStorm[2] should have support for both 
remote V8 debugging and TypeScript autocompletion & refactoring. It might 
serve as an all-in-one replacement for Visual Studio and Node Inspector for 
your TypeScript development.

[1] https://github.com/joyent/node/blob/master/src/node.cc#L2860
[2] http://www.jetbrains.com/webstorm/

-- 
-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to