Node.js Debugger ends as soon as it is attached

Question

I'm currently using WebStorm as IDE and my project uses pm2 as process manager. The structure of my ecosystem is the following:

module.exports = {
  name: 'myProject',
  cwd: __dirname,
  script: 'npm',
  args: 'run start:debug',
};

which executes

"start:debug": "nodemon --config nodemon-debug.json"

As soon as the project starts, the terminal throws:

Debugger listening on ws://127.0.0.1:9229/24bd6549-1601-4b0d-9e36-495765176abc
For help, see: https://nodejs.org/en/docs/inspector

I then press the Debug button in WebStorm with the following configuration:

After that the terminal shows this and the project starts without debugger:

Debugger listening on ws://127.0.0.1:9229/24bd6549-1601-4b0d-9e36-495765176abc
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Debugger ending on ws://127.0.0.1:9229/24bd6549-1601-4b0d-9e36-495765176abc
For help, see: https://nodejs.org/en/docs/inspector

My node version:

nvm current -> v14.20.1

Yesterday it worked fine, today I turned on my PC and it is broken, nothing on my environment has changed that I'm aware of.

score 20 · Accepted Answer · edited Apr 06 '23 at 09:47

20

It turns out the last version of WebStorm, 2022.3.3, broke the WebStorm debugger, I had to go back to version 2022.3.2.

edited Apr 06 '23 at 09:47

Mark Rotteveel

100,966
191
140
197

answered Mar 10 '23 at 16:53

Jhoan Nicolas Andres Becerra Q

543
4
14

Try 2022.3.4 when it will be released (or current 2023.1 EAP/Beta builds) -- it *should* do better there. If you have a time of course. – LazyOne Mar 12 '23 at 14:58
2

Both 2022.3.2 and 2023.1 EAP fixed this for me, thanks! – Shadorian Mar 13 '23 at 01:24
I spent so much time wondering whether it was the chrome update that broke. Downgrading worked fine. – Kaushal Mar 14 '23 at 10:56
See https://intellij-support.jetbrains.com/hc/en-us/community/posts/10524633222162/comments/10526858015250 – LazyOne Mar 14 '23 at 23:50
1

Downgrading to 2022.3.2 worked. – Sebastian Mar 16 '23 at 08:56
I was about to break the laptop, downgrading saved me, thanks =) – tuku Mar 16 '23 at 15:12
downgrading to IntelliJ IDEA 2022.2.5 (Ultimate Edition) worked for me. Upgrading to the latest 2023.1 Release Candidate build (For IDEA) did not work. – edcrates Mar 19 '23 at 20:23

score 2 · Answer 2 · answered Mar 16 '23 at 18:36

2

2023.3.4 was just released and should fix this issue.

answered Mar 16 '23 at 18:36

STRTUP

31
5

Node.js Debugger ends as soon as it is attached

2 Answers2