You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on a Node.js project with Jest unit tests. I am using the launch configuration i've pasted below to run the jest tests. If I put a break point on line 280, when I run the debugger the break point is now on line 270.
This did not happen on the older version of VS Code I had on my previous laptop (a Lenovo Thinkpad w541) And began only once I got a new laptop (Dell precision 5530) and installed the current version of VS Code.
Issue Type: Bug
I am working on a Node.js project with Jest unit tests. I am using the launch configuration i've pasted below to run the jest tests. If I put a break point on line 280, when I run the debugger the break point is now on line 270.
This did not happen on the older version of VS Code I had on my previous laptop (a Lenovo Thinkpad w541) And began only once I got a new laptop (Dell precision 5530) and installed the current version of VS Code.
My Launch Configuration
{
"type": "node",
"request": "launch",
"name": "Jest Tests (Windows)",
"program": "${workspaceRoot}\node_modules\jest\bin\jest.js",
"args": ["-i"],
"internalConsoleOptions": "openOnSessionStart",
"outFiles": ["${workspaceRoot}/dist/**/*"]
}
VS Code version: Code 1.28.1 (3368db6, 2018-10-11T18:13:53.910Z)
OS version: Windows_NT x64 10.0.17134
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: