Webstorm node debugger12/10/2023 ![]() ![]() Remote debugging, in public preview: You can now choose to remote debug your Node.JS applications running on App Service on Linux. One that I was interested in was this one: Just delete "-debug-brk=" in "Node parameters" field ("Debug Web" run configuration) and it should work as expected.Remote debugging of Node.js apps on Azure App Service from WebStorm Edit on GitHubĪt Microsoft Build 2018, a number of Azure App Service on Linux enhancements were announced. But "Debug Web" console is waiting for connection from port 29855 (that's why you see "cannot connect" there). "Debug Web slave#1" console resumes application execution using port 1337. That's why you see the second console ("Debug Web slave#1"). So WebStorm starts "Node.js Remote Debug" run configuration associated with 1337 port. What happens next is that WebStorm sees that another debug port (1337) is opened and assumes that it's the debug port of a child node process. But according to the output ("debugger listening on port 1337" line) the application's debugger is actually started on port 1337. WebStorm assumes that the application would be ready for debugging on port 29855 and waits for the connection. The first parameter "-debug-brk=29855" is appended by WebStorm and the second one is taken from "Node parameters" field of "Debug Web" run configuration. Note that the command line contains two duplicated parameters "-debug-brk=29855" and "-debug-brk=1337". Now, if I run it in debug mode, two debug consoles opened: Debug Web: "D:\Logiciels installés\nodejs\node.exe" -debug-brk=29855 -debug-brk=1337 web-server\app.js ![]() To resume it a Node.js remote debug session should be started with the same port. That's expected, because your "Debug Web" run confuguration has "-debug-brk=1337" argument that makes Node.js app suspend right after startup. When I click on Run: D:\Logiciels installés\nodejs\node.exe" -debug-brk=1337 web-server\app.js Thanks.Įdit: Error: Failed to lookup view ".\views\game\layout.ejs"Īt (C:\wamp\(C:\wamp\ (C:\wamp\(C:\wamp\param (C:\wamp\Router._dispatch (C:\wamp\www\Ayolan\web-server\node_modules\express\lib\router\index.js:173:5) When I run the Debug mode, the Debug Web debugger tab try to connect to 127.0.0.30xxx, a random port around 30000, but fail and then display the "cannot connect".ĭoes someone understand what's going on? Because I don't. Sometimes when I try to reach the webpage I got something like this in the webpage: Type: connect I got nothing on the console but I got "connected to 127.0.0.1:1337" on the Debugger tab. The second debug console "Debug Web slave #1": (v0.1.11)īut if I go on the tab "Debugger" I got a "cannot connect". Grunt-cli: The grunt command line interface. Web server has started in development mode. Now, if I run it in debug mode, two debug consoles opened:ĭebug Web: "D:\Logiciels installés\nodejs\node.exe" -debug-brk=29855 -debug-brk=1337 web-server\app.js When I click on Run: "D:\Logiciels installés\nodejs\node.exe" -debug-brk=1337 web-server\app.jsīut I got nothing if I go on the webpage, just this error: Code d'erreur : ERR_CONNECTION_ABORTED. (use the webservice on the port 1500 to reach it) There are my configurations, I actually have three servers (use pomelo.js), one for the web, one as webservice, hosted on the game server and the game-server that basically is not reachable from http request directly. ![]() I'm trying again today, but I got the same result. ![]() I tried few weeks ago to make the webstorm debugger works, but it didn't. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |