Latest PyCharm EAP disables remote Node JS debugging
PyCharm 2017.3 EAP (Professional Edition)
Build #PY-173.3188.29, built on October 11, 2017
PyCharm EAP User
Expiration date: November 10, 2017
JRE: 1.8.0_152-release-1024-b5 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.13
I just upgraded to the latest PyCharm 2017.3 EAP today (from the previous EAP) and now my Node JS Remote debug configuration is broken. The IDE tells me that the appropriate plugin is missing
I looked in the Plugins list and saw a "Node.js Remote Interpreter" plugin, but installing it hasn't brought back the functionality. This is a blocker for me in my NodeJS project. Any idea what happened?
I see the following in the Event Log:
Plugins Suggestion
Plugin supporting feature (Run Configuration[NodeJSRemoteDebug]) is currently not installed.
Configure plugins...
Ignore Unknown Features
All I did was upgrade PyCharm. The Node JS remote debugger was working fine before.
请先登录再写评论。
WebStorm's debugger (and hence PyCharm's NodeJS debugger) is under heavy development at the moment on the remote debugging. Sorry about that. Their EAP usually is one step ahead of PyCharm's for the Node stuff, if you'd like to give it a try and see if it is working.
But if that piece is critical for you, to save your sanity, sit out the next couple of PyCharm EAPs and wait for it to settle down. Just use the released version.
Thanks. I'm guessing they're phasing out the old-style node remote debugging (TCP-based) in favor of the Node 8 Websocket debugger... which is the Chromium Remote configuration type. I'm getting burned on a project that's still on an older NodeJS.
Is it safe to roll back from PyCharm 2017.3 EAP to the currently released version?
Correct, for both the NodeJS remote debugger and the Chromium debugger, they're switching in the direction of off-the-shelf protocols. You can track the progress in WebStorm's youtrack.jetbrains.com section.
Yes, should be fine to roll back. If you have any issue, though, move your project's .idea directory out of the way.
Ended up using this an an excuse to move my app to the latest Node version. Then it was just a simple matter of updating my package.json to specify `--inspect=...` instead of `--debug=...` and creating a Chromium Remote configuration to replace the NodeJS Remote Debug config.