Unable to debug Jest tests using VSCode

[marcantoineveilleux]

With the default project, I am unable to set breakpoint in visual studio code.

Here's my launch.json:

{
  // http://markuseliasson.se/article/debugging-jest-code/
    "version": "0.2.0",
    "configurations": [
        {
          "name":"Jest Tests",
          "type":"node",
          "request":"launch",
          "program":"${workspaceRoot}/node_modules/jest-cli/bin/jest.js",
          "stopOnEntry":false,
          "args":[
              "--runInBand"
          ],
          "cwd":"${workspaceRoot}",
          "preLaunchTask":null,
          "runtimeArgs":[
              "--nolazy"
          ],
          "env":{
              "NODE_ENV":"development"
          },
          "console":"integratedTerminal",
          "sourceMaps":false
        }
    ]
}

[alexjoverm]

Hi @marcantoineveilleux. I'm sorry but I don't think this issue belongs to this repository.

If you can set breakpoints with ts-jest, you should be able to do it here. So I suggest better ask in stackoverflow about it ot open an issue in ts-jest.

Nonetheless, I'll keep this issue open some days in case someone knows the answer

[mattmazzola]

I had opened similar issues on VSCode and Jest repos.
Two things, it only works with legacy protocol (not inspect), and it does not work with Node 7 or 8 due to breaking changes in the vmContext stuff.

Root Issue:
nodejs/node#7593

See related issues:
microsoft/vscode#28007
jestjs/jest#3748

[tonysneed]

@mattmazzola This launch.json file works for me. I'm able to set breakpoints and hit them.

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Tests",
      "type": "node",
      "request": "launch",
      "program": "${workspaceRoot}/node_modules/jest/bin/jest.js",
      "sourceMaps": true,
      "runtimeArgs": [
        "-i"
      ],
      "env": {
        "NODE_ENV": "development"
      },
      "outFiles": [
        "${workspaceRoot}/dist/**/*"
      ],
      "cwd": "${workspaceRoot}"
    }
  ]
}

The weird thing is that I have to press F5 twice, because the first time the debugger exits without hitting the breakpoint. But it hits the breakpoint the second time through. 😄