VS Code breakpoint with tsx and Nodejs 20.12.0 does not work

[piquark6046]

Acknowledgements

• I searched existing issues to avoid duplicates
• I understand this is a place to report a confirmed bug (not seek debugging help)
• I understand this is a collaborative open source project, and relies on community contributions
• I have read and understood the Contribution guide

Minimal reproduction URL

List-KR/multithread-array#1

Version

4.7.1

Node.js version

20.12.0

Package manager

npm

Operating system

Linux

Problem & expected behavior (under 200 words)

• What happened: All VS Code breakpoints are ignored

• What I expected: VS Code breakpoint works as using Node.js 20.11.1

• Screenshot:

  Screenshot

  

• devcontainer.json

  {
      "name": "Typescript with Rust",
      "image": "mcr.microsoft.com/devcontainers/base:ubuntu",
      "features": {
    	  "ghcr.io/devcontainers/features/node:latest": {
    		  "nodeGypDependencies": true,
    		  "version": "lts"
    	  },
    	  "ghcr.io/devcontainers/features/rust:latest": {
    		  "version": "latest",
    		  "profile": "default"
    	  },
    	  "ghcr.io/devcontainers-contrib/features/bash-command:latest": {
    		  "command": "echo hi!"
    	  },
    	  "ghcr.io/devcontainers-contrib/features/npm-package:latest": {
    		  "package": "typescript",
    		  "version": "latest"
    	  },
    	  "ghcr.io/devcontainers-contrib/features/typescript:latest": {
    		  "version": "latest"
    	  },
    	  "devwasm.azurecr.io/dev-wasm/dev-wasm-feature/rust-wasi:latest": {}
      },
      "remoteUser": "root",
      "mounts": [
    	  "source=${localEnv:HOME}/repos/Filters,target=/workspaces/resources/Filters,type=bind,consistency=cached",
    	  "source=${localEnv:HOME}/repos/Userscript,target=/workspaces/resources/Userscript,type=bind,consistency=cached"
      ]
  }

Contributions

• I will open a pull request for this issue
• I will support the work financially (any amount helps)

[piquark6046]

Is the reproduction information not enough?

[privatenumber]

Took a glance and the first few pages of files I scrolled had nothing to do with tsx or VSCode.
Please keep it minimal as it costs me time to help.

[tenpaMk2]

Hi @privatenumber . Thank you for developing.

I can reproduce in the minimal project.

• tsx-vscode-debug-not-working

VSCode cannot stop at the breakpoints via Node 20.12.0.

However, it can do via Node 20.11.1.
So, I think it's a problem of Node.

• Mac OS: Sonoma 14.4.1
• VSCode: February 2024 (version 1.87)
• Node: 20.12.0
• tsx: 4.7.1

Both Node 21 and 20 are not working at tsx when debugging...
I think it's too difficult situation for tsx users...

[privatenumber]

Thanks @tenpaMk2

Would you or @piquark6046 be willing to investigate this?

I'm not personally affected by this so I'm unlikely to work on it unless paid to.

[privatenumber]

@piquark6046

This is a project I work on for fun, primarily to improve my own workflow.

I'm not currently affected by this (maybe in the future), and it makes more sense for those that are affected by it to fix it.

I already donate my time to open source and maintain tsx to help others, and I'm not trying to take on more unpaid work.

I'd be happy to review and help you with your PR though.

[cenfun]

It seems that the root cause is because inline sourcemap no longer works in nodejs 20.12.0. VSCode debug might not work if there is no inline sourcemap.

• (typeof Error.prepareStackTrace !== "function") === false in nodejs 20.12.0, (see change lib: expose default prepareStackTrace nodejs/node#50827) but it is true in nodejs 20.11.0
• tsx used above to install inline sourcemap, see https://github.com/privatenumber/tsx/blob/develop/src/source-map.ts#L21

Hope this helps you.

[privatenumber]

Ah very helpful @cenfun, great work!

Would you be willing to open a PR?

[bqp-articulate]

I can confirm this behavior, and I'll add that I can also reproduce with the tsx smoketests in 20.12. If @cenfun isn't submitting a PR for this, I'd be happy to - I've invested time already wrapping my head around this bit of code and I have a workaround by pinning my environment to node 20.11

[cenfun]

@bqp-articulate there is PR here #517

[cenfun]

@privatenumber I create a new PR here #518
Could you please review it?

[privatenumber]

Released in v4.7.2!

Thanks for your contribution @cenfun 🙌!

[bqp-articulate]

I tested 4.7.2 on my end, works great. Thanks all!