vscode: Debugger won't hit break points with Jest test

Issue Type: Bug

Run debug with the following debugger setup:

{
      "name": "Debug Jest Tests",
      "type": "node",
      "request": "launch",
      "port": 9229,
      "runtimeArgs": [
        "--inspect-brk",
        "${workspaceRoot}/node_modules/.bin/jest",
        "--watch",
        "--bail",
        "--runInBand"
      ],
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "runtimeExecutable": "${env:HOME}/.nvm/versions/node/v8.11.1/bin/node",
      "skipFiles": [
        "lodash.js",
        "zone.js",
        "tslib.js",
        "angular",
        "browser-sync*",
        "pdf-make*"
      ]
    },

Getting this error in the CALL STACK pane and no breakpoints are hit.

[node-debug2] Error processing "stackTrace", Cannot read prop "replace" of null.

VS Code version: Code - Insiders 1.26.0-insider (d1272ff8edbaa54c81382f82fa2091f63ed3daea, 2018-07-17T08:29:57.116Z) OS version: Darwin x64 17.7.0

System Info
Item Value
CPUs Intel® Core™ i7-6820HQ CPU @ 2.70GHz (8 x 2700)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: enabled
rasterization: enabled
video_decode: enabled
video_encode: enabled
vpx_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 2, 2, 2
Memory (System) 16.00GB (1.37GB free)
Process Argv /Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron -psn_0_1179936
Screen Reader no
VM 0%
Extensions (15)
Extension Author (truncated) Version
string-converter ada 0.1.1
vscode-eslint dba 1.4.12
tslint eg2 1.0.34
auto-rename-tag for 0.0.15
githd hui 1.2.0
typelens kis 1.5.0
vsliveshare ms- 0.3.395
team ms- 1.136.0
debugger-for-chrome msj 4.8.0
typescript-hero rbb 2.3.2
vscode-icons rob 7.24.0
sass-indented rob 1.4.9
shader sle 1.1.3
move-ts str 1.11.3
sort-lines Tyr 1.7.0

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 2
  • Comments: 21 (7 by maintainers)

Most upvoted comments

This one was specifically for the error Cannot read prop "replace" of null. which sounds like it went away, so I’m going to close it, but you can open a new one @rswerve. Looking at your log, I see you set breakpoints in a file but I don’t see that file being loaded.

Would I be better off opening a new issue with the debug details? Not sure this one is being checked anymore.