Waiting to connect to debug instance
I've done a tone of remote debugging with webstorm, so I'm mostly confident I'm not making a user mistake.
I start my app with an of the following:
- node --inspect-brk=<my custom port here> app/app
- node --inspect-brk app/app.js
- node --inspect=<my custom port here> app/app
- node --inspect app/app
I then create a node.js remote debug configuration with the proper host and port (the host in my case is 127.0.0.1 as my instance isn't containerized and is running locally).
Result: Console says "connecting to 127.0.0.1:9229" indefinitely (or whatever port I'm attempting to connect on).
Anyone else experiencing this?
I'm using WebStorm EAP 2107.2 and it's been working fine until today.
Please sign in to leave a comment.
What's curious to me is that node gives output:
ws://127.0.0.1:9230/add5135e-12ae-40c3-9939-dc2ac5f20892
That random hex string path seems significant. I feel like webstorm might need to know that path in order to connect??
I've tested node inspect CLI and that can successfully attach
Node.js Remote run configuration can only be used when debugging with TCP-based Protocol (Node.js < 7.x).
To remotely debug application with Chrome Debugging Protocol (with `--inspect`/`--inspect-brk`), you need using Chromium Remote run configuration
- run your app with `node --inspect-brk=<my custom port here> app/app`
- create a Chromium Remote run configuration, specify your custom port as a Port: there, press Debug
Elena - that works.
I swear I was using node.js debugger before with node 8. I mean, I upgraded to node 8 weeks ago, and also upgraded to webstorm eap 2017.2 in order to debug on node 8, and I have definite memories of debugging that way, and I've never used Chromium Remote before now. Either I'm taking crazy pills, or something changed.
I guess that point is moot anyhow - chromium remote is working fine and I'm unblocked and productive again. thanks for the help :)