Vscode node debugger not stopping on breakpoints when launching with nodemon

[TitaneBoy]

• VSCode Version: 1.10.2
• OS Version: Windows 7 Profesionnal, SP1

Hi everyone.

I'm trying to debug typescript code (or javascript code) in server side with visual studio code, when launching it with nodemon. I've added a new configuration in launch.json which looks like this:

{
      "type": "node",
      "request": "launch",
      "name": "Launch server with Nodemon",
      "runtimeExecutable": "nodemon",
      "runtimeArgs": [
        "--debug=5858"
      ],
      "program": "${workspaceRoot}/src/server.ts",
      "restart": true,
      "port": 5858,
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "outFiles": ["${workspaceRoot}/build/**/*.js"]
    }

I have a task in vscode that is running tsc that builds javascript files properly. This is my current task config:

{
  // See https://go.microsoft.com/fwlink/?LinkId=733558
  // for the documentation about the tasks.json format
  "version": "0.1.0",
  "command": "tsc",
  "isShellCommand": true,
  "args": ["-p", "."],
  "showOutput": "silent",
  "problemMatcher": "$tsc"
}

The javascript files are generated as expected when I change a typescript file.
And the nodejs server is restarting as expected when a javascript file is generated.

But I am not able to break on any breakpoint (on typescript files or javascript files).

Can you tell me please if it is an issue or if there is something I am missing ?

Thank you for your help

[roblourens]

Does your tsc setup build sourcemaps? Does it work without nodemon?

[TitaneBoy]

Hi @roblourens . Yes, my tsc setup builds sourcemaps. Without the nodemon configuration, I can break on typescript breakpoints.
Here is my other vscode launch configuration where breaking is working:

{
      "type": "node",
      "request": "launch",
      "name": "Lancer le programme",
      "program": "${workspaceRoot}/src/server.ts",
      "args": [
      ],
      "outFiles": ["${workspaceRoot}/build/**/*.js"]
    }

[roblourens]

Does it work with nodemon and "protocol": "inspector"?

[TitaneBoy]

It looks to work (i.e to break) now when I add the "protocol": "inspector" in my launch configuration. In the terminal console, it shows however a warning saying that it is an experimental feature (I guess it talks about the inspector protocol ?)

Is it the right way to do in order to break on breakpoints with nodemon ? Or there is still an issue in vscode ? Because in the docs, they don't talk about adding inspector protocol when using nodemon

Thanks for your answer

[roblourens]

It shouldn't be required but the inspector protocol adapter sometimes works with more sourcemap configs.

[philipmat]

I seem to be able to reproduce this with v1.11.2 on Windows 10 with node v7.9.0.

Starting an express app (JS not TS) with ./node_modules/.bin/nodemon --debug ./bin/www ./, if I use "port": 5858, "protocol": "legacy" in launch.json - my breakpoints are "red" but the debugger stops on none of them.

Starting an express app with ./node_modules/.bin/nodemon --inspect ./bin/www ./, and "port": 9229, "protocol": "inspector" - my breakpoints are "gray" and the text reads "Breakpoint ignored because generated code not found."

--inspect / "protocol": "inspector" seems to be working fine on OS X El Capitan v10.11.6.

[TitaneBoy]

Hi everyone.

It seems that I have the same issue again but this time, it looks a little different.

I'm using now the last version of vscode (1.12.2 but I have the same issue with 1.12.1)
To be sure the issue is not related to my code, I've created a tiny simple project just to be able to break in the main when debugging with nodemon

Here is my package.json config:

{
  "name": "test_typescript",
  "version": "1.0.0",
  "description": "",
  "main": "main.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@types/node": "^7.0.18",
    "nodemon": "^1.11.0",
    "tslint": "^5.2.0",
    "tslint-eslint-rules": "^4.0.0",
    "typescript": "^2.3.2",
    "vrsource-tslint-rules": "^5.1.0"
  }
}

As you can see, I've installed typescript and nodemon locally in the project.

Here is my tasks.json config:

{
  // See https://go.microsoft.com/fwlink/?LinkId=733558
  // for the documentation about the tasks.json format
  "version": "0.1.0",
  "command": "${workspaceRoot}/node_modules/.bin/tsc",
  "isShellCommand": true,
  "args": ["-w", "-p", "."],
  "showOutput": "silent",
  "problemMatcher": "$tsc"
}

Here is my tsconfig.json config:

{
    "compileOnSave": true,
    "compilerOptions": {
        "sourceMap": true,
        "watch": true,
        "noImplicitAny": true,
        "outDir": "./build",
        "target": "es5",
        "alwaysStrict":true,
        "declaration": true,
        "declarationDir": "./types",
        "noFallthroughCasesInSwitch":true,
        "noUnusedLocals":true,
        "noUnusedParameters":true,
        "pretty": true,
        "lib": [
            "es6",
            "es5",
            "es7"
        ]
    },
    "include": [
        "./src/**/*"
    ]
    ,
    "exclude": [
        "./build",
        "./node_modules",
        "**/*.spec.ts"
    ]
}

And Finally, here is my launch.json config:

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "launch",
      "name": "Launch Main with nodemon",
      "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/nodemon",
      "runtimeArgs": [
        "--inspect=5858"
      ],
      "program": "${workspaceRoot}/src/main.ts",
      "restart": true,
      "port": 5858,
      "protocol": "inspector",
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "outFiles": [
        "${workspaceRoot}/build/**/*.js"
      ],
      "sourceMaps": true
    },
    {
      "type": "node",
      "request": "launch",
      "name": "Lancer le programme",
      "program": "${file}",
      "outFiles": [
        "${workspaceRoot}/build/**/*.js"
      ]
    }
  ]
}

I have only 2 folders in my project: "src" which contains main.ts file and "build" which is the output directory for generated javascript files.

Here is my main.ts file:

const Myvar = 5;

console.log("Hello");
console.log(Myvar);

As you can see, it's very simple. I've added a breakpoint in main.ts and when I debug with nodemon, this is what happens:

• The main.js and its map are correctly generated
• The breakpoint is never reached and vscode execute the main.ts until the end
• After 10 secs, I have the following message

Cannot connect to runtime process, timeout after 10000 ms - (reason: Cannot connect to the target: connect ECONNREFUSED 127.0.0.1:5858).

I don't understand why this is happening and what I can do to fix it. Can you help me please ?

Thank you for your answer

[TitaneBoy]

This is what I can see in the console output:

C:\Personal_Data\My_Setup\Node.js\Test_Typescript>cd c:\Personal_Data\My_Setup\Node.js\Test_Typescript && c:\Personal_Data\My_Setup\Node.js\Test_Typescript/node_modules/.bin/nodemon --inspect=
5858 build\main.js
[nodemon] 1.11.0
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `node --inspect=5858 build\main.js`
Debugger listening on port 5858.
Warning: This is an experimental feature and could change at any time.
To start debugging, open the following URL in Chrome:
    chrome-devtools://devtools/remote/serve_file/@60cd6e859b9f557d2312f5bf532f6aec5f284980/inspector.html?experiments=true&v8only=true&ws=127.0.0.1:5858/22488366-9fca-4840-9bd4-1e983a19566e
Hello
5
[nodemon] clean exit - waiting for changes before restart

[TitaneBoy]

@roblourens @weinand : Do you have any idea of what I am missing or what is happening ? (see my 2 previous posts)

Thank you for your answers..

[weinand]

@TitaneBoy I suspect that your program is just too short: it terminates before the debugger can attach successfully. Please try with this program instead of your 2 console.logs:

var i = 0;
setInterval(() => {
	console.log('hello world:' + i++);
}, 1000);

And set the breakpoint on the 'console.log' line.

If you read the nodemon output carefully, you can see that your program has exited and that there is nothing to debug:

[nodemon] clean exit - waiting for changes before restart

Your program has terminated and nodemon will restart only if it detects source chnages.