Skip to content

fix(vscode): use tsx for 'Run Current File' debug configuration #25220

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
AjayBora002 wants to merge 5 commits into from
Closed

fix(vscode): use tsx for 'Run Current File' debug configuration #25220

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
890946c
fix(vscode): use tsx for 'Run Current File' debug configuration
AjayBora002 Apr 13, 2026
2716c2d
Merge branch 'main' into fix/vscode-run-current-file-ts
AjayBora002 Apr 13, 2026
cae79c2
Merge branch 'main' into fix/vscode-run-current-file-ts
AjayBora002 Apr 14, 2026
06b8795
Merge branch 'main' into fix/vscode-run-current-file-ts
AjayBora002 Apr 16, 2026
33ed711
Merge branch 'main' into fix/vscode-run-current-file-ts
AjayBora002 Apr 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions .vscode/launch.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,12 +41,17 @@
"localRoot": "${workspaceFolder}/packages"
},
{
"name": "CLI: Run Current File",

@spencer426 spencer426 May 22, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of the updates to .vscode/launch.json were already merged in PR #22894 is this still applicable? You will need to rebase this PR onto main to resolve conflicts.

"type": "node",
"request": "launch",
"name": "Launch Program",
"skipFiles": ["<node_internals>/**"],
"program": "${file}",
"outFiles": ["${workspaceFolder}/**/*.js"]
"runtimeArgs": ["--import", "tsx"],
"cwd": "${workspaceFolder}",
"console": "integratedTerminal",
"skipFiles": ["<node_internals>/**"],
"env": {
"NODE_ENV": "development"
}
Comment on lines +44 to +54

@gemini-code-assist gemini-code-assist Bot Apr 12, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Using npm exec as the runtimeExecutable in a launch.json configuration is problematic for debugging. VS Code's Node.js debugger attempts to inject debugging flags (such as --inspect-brk) into the runtimeExecutable. Since npm does not recognize these flags, it will likely fail to start or ignore them, preventing the debugger from attaching to the actual script process. This means breakpoints will not work as expected.

Additionally, npm exec introduces significant startup overhead. Since this project uses Node.js 20 (recommended ~20.19.0 per the repository style guide), the preferred approach is to use node directly with the --import tsx flag.

Furthermore, since this is a CLI project using Ink, you should set "console": "integratedTerminal" to ensure the output is rendered correctly in a TTY-enabled environment, consistent with other configurations in this file (e.g., lines 15, 72, 90).

Suggested change
"name": "CLI: Run Current File",
"type": "node",
"request": "launch",
"name": "Launch Program",
"runtimeExecutable": "npm",
"runtimeArgs": ["exec", "tsx", "--", "${file}"],
"cwd": "${workspaceFolder}",
"skipFiles": ["<node_internals>/**"],
"program": "${file}",
"outFiles": ["${workspaceFolder}/**/*.js"]
"outFiles": ["${workspaceFolder}/**/*.js"],
"env": {
"NODE_ENV": "development"
}
"name": "CLI: Run Current File",
"type": "node",
"request": "launch",
"program": "${file}",
"runtimeArgs": ["--import", "tsx"],
"cwd": "${workspaceFolder}",
"console": "integratedTerminal",
"skipFiles": ["<node_internals>/**"],
"env": {
"NODE_ENV": "development"
}
References
  1. The project recommends Node.js ~20.19.0 for development, which supports the --import flag for loaders. (link)

},
{
"type": "node",
Expand Down
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -372,8 +372,8 @@ npm run lint
2. In VS Code, use the "Attach" launch configuration (found in
`.vscode/launch.json`).

Alternatively, you can use the "Launch Program" configuration in VS Code if you
prefer to launch the currently open file directly, but 'F5' is generally
Alternatively, you can use the "CLI: Run Current File" configuration in VS Code
if you prefer to launch the currently open file directly, but 'F5' is generally
recommended.

To hit a breakpoint inside the sandbox container run:
Expand Down