ts-node: Breakpoints don't work

I was also having this issue, but I solved it with this:

Below is my before/after launch.json (using VSCode 1.59.0)

Before

"version": "0.2.0",
  "configurations": [
    {
      "name": "ts-node",
      "type": "pwa-node",
      "request": "launch",
      "runtimeArgs": ["--nolazy", "-r", "ts-node/register"],
      "protocol": "inspector",
      "args": ["--ts-node"],
      "program": "${workspaceFolder}/app.ts",
      "cwd": "${workspaceRoot}"
    }
  ]

After

"version": "0.2.0",
  "configurations": [
    {
      "name": "ts-node",
      "type": "pwa-node",
      "request": "launch",
      "runtimeArgs": ["--nolazy", "-r", "ts-node/register"],
      "protocol": "inspector",
      "args": ["${workspaceFolder}/app.ts", "--ts-node"],
      "cwd": "${workspaceRoot}"
    }
  ]

I removed program property and moved its value into args and it worked.

I don’t know why, but now vscode debugger hits breakpoints correctly

Are you using docker? If so, this comment helped to resolve this issue for me:

https://github.com/Microsoft/vscode-recipes/issues/187#issuecomment-483814483

This shows that hitting breakpoints should work as well, so there might be something else going on with your actual repository that prevents breakpoints from being hit.

---

info on my setup (sharing all of it just to be sure)

I’m using vscode 1.42.0, node 13.8 (from dockerhub), ts-node 8.6.2

My app is started using the following line:

export TS_NODE_PROJECT=tsconfig.json; export TS_NODE_FILES=true; node --nolazy --inspect=0.0.0.0:9229 -r ts-node/register ./src/index.ts

my tsconfig.json looks like the following:

{
	"compilerOptions": {
		"esModuleInterop": true,
		"strict": true,
		"lib": ["ES2020"],
		"types": ["node"],
		"sourceMap": true
	},
	"files": ["./src/**/*"]
}

my launch.json looks like the following:

{
	"version": "0.2.0",
	"configurations": [
		{
			"type": "node",
			"request": "attach",
			"name": "Docker: Attach to Node",
			"sourceMapPathOverrides": {
				"/usr/src/app/*": "${workspaceRoot}/*"
			},
			"port": 9229,
			"protocol": "inspector" // probably not needed here since vscode should resolve this automatically, even when using ts-node (Haven't tested it yet though)
		}
	]
}```

I wonder if it does not repro with mocha because mocha loads all the files first, then fires the callbacks later. Perhaps this delay gives the debugger enough time to register breakpoints.

On Tue, May 12, 2020 at 4:48 PM Roman Kozak notifications@github.com wrote:

@cspotcode https://github.com/cspotcode thank you for the sample. I think you are right that this is VSCode bug. I’ve tried to workaround by compiling the typescript code with tsc first and then running it - with this approach, breakpoints were triggered correctly in the test project, but in the other project only part of the time. This doesn’t repro when running code thru mocha test with ts-node, so this could an alternative approach to having breakpoint in the main file for VS Code users.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/TypeStrong/ts-node/issues/778#issuecomment-627585441, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC35OCB3PDYFT54J2KA4CDRRGYZFANCNFSM4GWLAV7A .

Facing the same issue with the VS Code debugger. It just doesn’t hit breakpoints.

@Neustart I am in the same boat, on Mac. I have been tracing and trying just about every suggestion from https://github.com/TypeStrong/ts-node/issues/537, to no avail. I’ve also tried all sorts of tsconfig.json tweaks (such as inline source maps, outDir configuration), etc etc. It seems ts-node is just not wired up to be able to inspect the files, but I have not yet figured out why the debugger can attach then have no files to debug. Would love to figure this out!