Previously, in order to debug my Node applications, I would run the following command:
concurrently node --max-old-space-size=8192 --inspect --debug-brk node_modules/grunt-cli/bin/grunt serve
Now, running the same command always yields:
Running "concurrent:dev" (concurrent) task
Unable to open devtools socket: address already in use
Warning: Unable to open devtools socket: address already in use Use --force to continue.
I thought that maybe the
concurrent portion of the command was causing this issue but upon removing it, the issue persisted.
I can open my
Resource Monitor on Windows and kill any tasks that are running on that port to make sure nothing else is using it, but it still fails.
As for my Grunt workflow, when
grunt serve is run, another task called
concurrent:dev is run which looks like:
command: path.resolve(__dirname, 'node_modules/.bin/ng build --watch')
Which finally runs
express:dev which looks like:
I’m currently using the
1.6.5 version of the Angular CLI,
3.10.8 of NPM and
6.9.1 of Node.
Have the debug settings changed since these versions? How can I successfully debug my Node application?