Breakpoint not hit

[dbaeumer]

Test case:

var i = 1000;
var s = "Hello Workd".repeat(8);

var obj = {
    name: "Dirk",
    surname: "Baeumer",
    address: {
        street: "Laendischstrasse",
        number: 5,
        optional: {
            type: "house"
        }
    }
}

console.log(obj);

console.log(obj);

Have a breakpoint on line 16 & 18. Run debugger.

• observe: first breakpoint is hit.
• press F10
• observe: second breakpoint is not hit

My tsconfig.json is:

{
    "compilerOptions": {
        "module": "commonjs",
        "target": "es6",
        "sourceMap": true
    }
}

task.json:

{
    "version": "0.1.0",
    "command": "tsc",
    "isShellCommand": true,
    "isWatching": true,
    "showOutput": "always",
    "args": [
        "--watch"
    ],
    "problemMatcher": {
        "base": "$tsc-watch"
    }
}

And launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch",
            "type": "node",
            "request": "launch",
            "program": "${workspaceRoot}/test.js",
            "stopOnEntry": false,
            "args": [],
            "cwd": "${workspaceRoot}",
            "runtimeExecutable": null,
            "runtimeArgs": [
                "--nolazy"
            ],
            "env": {
                "NODE_ENV": "development"
            },
            "externalConsole": false,
            "sourceMaps": true,
            "outDir": null
        },
        {
            "name": "Attach",
            "type": "node",
            "request": "attach",
            "port": 5858,
            "sourceMaps": false,
            "outDir": null
        }
    ]
}

node version: 4.2.6 

[isidorn]

@weinand can you please check this, my suspision is that it is some source map issue

[weinand]

@dbaeumer node 4.2.6 crashes when hitting the second console.log(). It is independent from the operating system and I can reproduce this in node-inspector.

[weinand]

I've filed this issue against node: nodejs/node#4917

[Raathigesh]

Could you please check after setting the outDirin launch.json ? I had the same issue and setting the outDirfixed it but I'm running node 4.1.2 though.