This is the error popping up as soon as I press the debug button: 11:38:49,751 INFO - #c.i.j.d.JavaScriptDebugProcess - JSDebugger publish port: 58315 Instructions are written for application generated with you might have a different setup.I'm running WebStorm 2022.2.2 on Windows and my Node.js project is sitting in WSL2 Ubuntu distribution, and I'm trying to get the debugger working for my setup with no success so far. ![]() When a child process is spawned with -debug option instead of -debug-brk, WebStorm debugger doesn't always have time to register a breakpoint when the process starts, and thus breakpoints in child process are not hit. This should fix problem debugging Grunt child processes - by default, the spawned child process uses the same debug port as a parent process - as a result the forked process is suspended and the application 'stalls'.Īlso, open node_modules\grunt-express-server\tasks\lib\server.js and change line 71 to: ('-debug-brk') JavaScript file: path/to/node_modules/grunt-cli/bin/gruntĪdd the following line to the top of your Gruntfile.js process.execArgv = Use Node.js run configuration to debug: Working directory: your project root folder In general, to be able to debug the server-side code of your angular-fullstack application, I'd suggest the following: ![]() There are multiple issues there, related to WebStorm, Grunt, Node itself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |