Useful or not, from you.
vscode `Unknown file extension ".ts"` error debugging typescript app in Node app when upgrading from 1.46.1 to 1.47.2

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->

  • VSCode Version: 1.47.2
  • OS Version: Windows 10

Steps to Reproduce:

  1. In 1.46.1 click F5 in folder with Node app using Typescript
  2. App runs in debug mode fine
  3. Upgrade to 1.47.2
  4. click F5 in folder with Node app using Typescript
  5. Error occurs (see below)

This happens with multiple projects.

<!-- Launch with code --disable-extensions to check. --> Does this issue occur when all extensions are disabled?: Yes

Error message:

"C:\Program Files\nodejs\node.exe" "c:\........\app.ts"
Debugger listening on ws://127.0.0.1:60898/8098207d-8ea6-4dc0-9893-7cedba10fb1f
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
Waiting for the debugger to disconnect...
internal/modules/run_main.js:54
    internalBinding('errors').triggerUncaughtException(
                              ^

TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for c:\........\app.ts
    at Loader.defaultGetFormat [as _getFormat] (internal/modules/esm/get_format.js:65:15)
    at Loader.getFormat (internal/modules/esm/loader.js:113:42)
    at Loader.getModuleJob (internal/modules/esm/loader.js:243:31)
    at async Loader.import (internal/modules/esm/loader.js:177:17) {
  code: 'ERR_UNKNOWN_FILE_EXTENSION'
}
Process exited with code 1

launch.json:

{
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
  {
    "type": "node",
    "sourceMaps":true,
    "request": "launch",
    "name": "Launch Program",
    "skipFiles": [
        "<node_internals>/**"
    ],
    "program": "${workspaceFolder}/src/app.ts",
    "outFiles": [
        "${workspaceFolder}/out/**/*.js"
    ],
    "env": {
    }            
  }
  ]
}
That's a useful answer
Without any help

It is, and we have some tests for it, but it looks like there's something that might not work at parity with node-debug's treatment.

Since I know it works in some cases and this is an uncommon case with an easy workaround, I didn't triage it for July, but will tackle it during debt week or the upcoming iteration.