You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see the node process in the "attach to process" window, but when I try to attach Visual studio shows a message box with a timeout error.
This is what I've done:
Changed current directory to my nwjs project
Started the app with: C:\nwjs-v0.12.2-win-ia32\nw.exe --remote-debugging-port=9222 "."
(tcpview shows nw.exe listening on port 9222)
Opened attach to process window in Visual Studio, entered "Transport: Node.js remote debugging", "Qualifier: tcp://localhost:9222/#ping=0", and hit refresh
Selected the node.exe entry in the list and hit attach
(Message box appears with something like "attaching not possible, timeout", but tcpview shows established connections to Visual Studio.)
I believe that Nw.js is using the Chrome debug protocol, not the v8/Node debug protocol that we currently support, and that's why attachment fails.
With the Chrome debug protocol having now landed in Node proper, and the V8 debug protocol deprecated, we do plan on adding support for the Chrome debug protocol as part of a larger debugging effort sometime in the future.
Hi,
is it possible to debug the code running in the node part of a node-webkit (nwjs) application?
(Attach the remote debugger etc.?)
Regards
Andreas
The text was updated successfully, but these errors were encountered: