Debugging tsx via NPM does not work if console is set to integratedTerminal or externalConsole, only internalConsole works

[GoldenretriverYT]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.92.2
• OS Version: Windows_NT x64 10.0.22631

Steps to Reproduce:

1. Create a new folder
2. npm init, install tsx as dev dependency. Create a npm task that runs npx tsx file.ts, and a launch.json profile that runs that task.
3. Set the launch tasks "console" property to "integratedTerminal", the debugger will attach at first but dettach before the code is actual ever ran.
4. If you, on the other hand, set it to "internalConsole" it works fine.

Also tested in Insiders with default extensions, same issue. Also happens with ts-node in place of tsx.

[connor4312]

I cannot reproduce this. Please check your terminal configuration and dotfiles (e.g. npmrc) to see if you have anything that would overwrite the NODE_OPTIONS environment variable, as this will break debugging.

[GoldenretriverYT]

I recently reset my computer and haven't done a lot since, so I doubt its that (and i didnt find anything suspicious). And printing NODE_OPTIONS in Node shows that they dont seem to be changed from what vscode passes:

vvvv passed by vscode

vvvv both variables in node

[connor4312]

Strange can you run the Developer: Toggle Developer Tools command and check for any errors that might have been logged there?

[GoldenretriverYT]

no errors :/

[GoldenretriverYT]

Modifying the launch.json to directly use tsx or ts-node without a npm task works, so I assume it somehow breaks because of npm being inbetween?

[connor4312]

Got it. Last question, can you share the contents of C:\Program Files\nodejs\npm.cmd?

I think the command is likely running a Node process before tsx, which is being attached to in order to debug, but then by the time it launches your real program the debugger thinks it already finished.

[GoldenretriverYT]

Sure

:: Created by npm, please don't edit manually.
@ECHO OFF

SETLOCAL

SET "NODE_EXE=%~dp0\node.exe"
IF NOT EXIST "%NODE_EXE%" (
  SET "NODE_EXE=node"
)

SET "NPM_PREFIX_JS=%~dp0\node_modules\npm\bin\npm-prefix.js"
SET "NPM_CLI_JS=%~dp0\node_modules\npm\bin\npm-cli.js"
FOR /F "delims=" %%F IN ('CALL "%NODE_EXE%" "%NPM_PREFIX_JS%"') DO (
  SET "NPM_PREFIX_NPM_CLI_JS=%%F\node_modules\npm\bin\npm-cli.js"
)
IF EXIST "%NPM_PREFIX_NPM_CLI_JS%" (
  SET "NPM_CLI_JS=%NPM_PREFIX_NPM_CLI_JS%"
)

"%NODE_EXE%" "%NPM_CLI_JS%" %*

[connor4312]

FOR /F "delims=" %%F IN ('CALL "%NODE_EXE%" "%NPM_PREFIX_JS%"') DO (

that would do it

[marluanespiritusanto]

@connor4312 I’m in the same situation, but on MacOS, after updating to Sequoia. How would it be in this case?