.@phpstorm Is there any documentation about how to debug a #Nodejs app in a #Docker #container in #webstorm ? Attaching a debugger just doesn't seem to work
-
-
Replying to @bassamjarad @phpstorm
Hey, please have a look at this tutorial: https://blog.jetbrains.com/webstorm/2017/04/quick-tour-of-webstorm-and-docker/ … Here you have a run configuration that runs the app in Docker and then the IDE attaches the debugger. What was the problem with the Attach configuration? Ports?
2 replies 0 retweets 3 likes -
Replying to @WebStormIDE @phpstorm
b/c it should've been --inspect-brk. Also, the webserver is not working in debug. So, webserver is not working and breakpoints are not being triggered. About ports, I don't see how WS is mapping debug port from container to local for debug to work correctly
2 replies 0 retweets 0 likes -
Replying to @bassamjarad @phpstorm
If you're using the Attach to Node.js configuration, you need to configure port mapping yourself when running the container or expose all ports.
2 replies 0 retweets 0 likes -
Replying to @WebStormIDE @phpstorm
Same steps are not working for Nodejs v8 or v10. Please check the screenshotspic.twitter.com/NxTSZQwlku
1 reply 0 retweets 0 likes -
Replying to @bassamjarad @phpstorm
Can you please try PhpStorm 2018.2.3 EAP: https://blog.jetbrains.com/phpstorm/2018/09/phpstorm-2018-2-3-eap-182-4323-64/ …
2 replies 0 retweets 0 likes -
Replying to @WebStormIDE @phpstorm
Upgraded ... still nothing. But I went ahead and tried the same config on
@code and to my surprise it worked right away
and breakpoints caught correctly!1 reply 0 retweets 0 likes -
Replying to @bassamjarad @phpstorm
Sorry, we don't have any other ideas on what might be causing the problem. Would appreciate it if you report a new issue and attach a sample project on our tracker: https://youtrack.jetbrains.com/issues/WEB Thank you!
2 replies 0 retweets 0 likes -
Replying to @WebStormIDE @phpstorm
I think this has been resolved in WEB-34537 . It's working perfectly now! Thanks
1 reply 0 retweets 0 likes
Great to hear that! Thanks for the update!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.