Can't set breakpoint on imported TypeScript project file

[garyking]

Type: Bug

In previous versions of VSC, I could set a breakpoint on imported TypeScript project code. Now, I must set the breakpoint in the compiled JavaScript code, rather than the original TypeScript code.

I have one NPM project, called my-project. I have another NPM project, called my-utils. I use yarn link so I can import my-utils into my-project with import * as myUtils from 'my-utils';. Both projects are TypeScript projects, that compile their code to JavaScript.

1. Open a file in my-project which imports my-utils.
2. Set a breakpoint in my-utils, in a .ts file, which should trigger when running a launch configuration.
3. Run the debugger. The breakpoint is not triggered. Any breakpoint set in the compiled JS code in my-utils gets triggered, however.

How can I get the previous functionality, where I can set breakpoints in imported .ts files?

Launch config:

{
  "type": "node",
  "request": "launch",
  "name": "list (ts-node)",
  "runtimeArgs": ["-r", "ts-node/register"],
  "skipFiles": ["<node_internals>/**"],
  "env": {
    "TS_NODE_LOG_ERROR": "true"
  },
  "args": ["${workspaceFolder}/src/cli.ts", "list"]
}

VS Code version: Code 1.73.0 (Universal) (8fa188b, 2022-11-01T15:38:50.881Z)
OS version: Darwin arm64 21.6.0
Modes:
Sandboxed: No

System Info

Item	Value
CPUs	Apple M1 (8 x 24)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off
Load (avg)	5, 6, 6
Memory (System)	16.00GB (0.12GB free)
Process Argv	--crash-reporter-id 33166f13-0cd4-4333-aabf-41b2210e787b
Screen Reader	no
VM	0%

Extensions (45)

Extension	Author (truncated)	Version
Bookmarks	ale	13.3.1
solargraph	cas	0.24.0
gitignore	cod	0.9.0
vscode-eslint	dba	2.2.6
gitlens	eam	13.0.4
EditorConfig	Edi	0.16.4
prettier-vscode	esb	9.9.0
auto-rename-tag	for	0.1.10
code-runner	for	0.11.8
html-slim-scss-css-class-completion	gen	1.7.8
todo-tree	Gru	0.0.219
RelativePath	jak	1.5.0
vscode-styled-components	jpo	1.7.0
center-editor-window	kai	2.3.0
dotenv	mik	1.0.1
goto-next-previous-member	mis	0.0.6
isort	ms-	2022.4.0
python	ms-	2022.18.1
vscode-pylance	ms-	2022.11.10
jupyter	ms-	2022.9.1202862440
jupyter-keymap	ms-	1.0.0
jupyter-renderers	ms-	1.0.12
vscode-jupyter-cell-tags	ms-	0.1.6
vscode-jupyter-slideshow	ms-	0.1.5
live-server	ms-	0.4.3
vscode-js-profile-flame	ms-	1.0.4
vscode-react-native	msj	1.10.0
color-highlight	nau	2.5.0
vscode-jest	Ort	4.6.0
vscode-css-peek	pra	4.2.0
ruby	reb	0.28.1
vscode-statusbar-json-path	ric	2.0.0
wikitext	Row	3.6.5
vscode-fileutils	sle	3.5.0
rewrap	stk	1.16.3
tabnine-vscode	Tab	3.6.19
sort-lines	Tyr	1.9.1
es-quotes	vil	0.2.6
highlight-matching-tag	vin	0.10.1
intellicode-api-usage-examples	Vis	0.2.6
vscodeintellicode	Vis	1.2.29
quokka-vscode	Wal	1.0.508
vscode-ruby	win	0.28.0
markdown-all-in-one	yzh	3.4.3
vscode-open-in-github	ziy	1.3.6

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848cf:30577861
nodejswelcome1:30587005
fc301958:30595537
282f8724:30602487
gswce2:30602635
iaj6b796:30602301
dbltrim-noruby:30604474

[HofmannZ]

Having the same issue, used to work up until a couple of days ago.

tasks.json

{
  "version": "2.0.0",
  "tasks": [
    {
      "type": "typescript",
      "tsconfig": "tsconfig.json",
      "problemMatcher": ["$tsc"],
      "group": {
        "kind": "build",
        "isDefault": true
      }
    }
  ]
}

launch.json

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "preLaunchTask": "npm: build",
      "request": "launch",
      "name": "Launch Program",
      "skipFiles": ["<node_internals>/**"],
      "program": "${workspaceFolder}/build/server/index.js",
      "outFiles": ["${workspaceFolder}/**/*.js"],
      "internalConsoleOptions": "openOnSessionStart"
    }
  ]
}

[connor4312]

/jsDebugLogs

[vscodenpa]

Please collect trace logs using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.

⚠️ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to connor@xbox.com

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[garyking]

@connor4312 Hello, I've attached the trace logs now, so please re-open this issue, thanks:

vscode-debugadapter-8e05496e.json.gz

What I did was create a test.ts file with:

import { createTable } from 'gary-utils';

function main(): void {
  const headings = ['a', 'b', 'c'];

  const rows = [
    ['a', 'a', 'a'],
    ['b', 'b', 'b'],
    ['c', 'c', 'c'],
  ];

  console.log(createTable(headings, rows));
}

main();

Then create breakpoints on console.log(createTable(headings, rows)); and within the imported createTable function. The first breakpoint works, but the second one doesn't.

[garyking]

Could the problem be caused by the fact that gary-utils is symlinked using yarn link?

I didn't have this problem a few months ago in VSC. But now when I install an older version of VSC, I still have this problem.