How to disable VSCode launch.json prioritize build folder

Question

I have the following configuration in my launch.json file

        {
            "type": "node",
            "request": "launch",
            "name": "Server - Current File",
            "program": "${file}",
            "cwd": "${workspaceFolder}/server",
            "runtimeExecutable": "tsx",
            "outputCapture": "std",
            "env": {
                "NODE_ENV": "development"
            }
        },

I am using it to run files from my src folder using tsx without running a full build. The problem is if a build folder exist it will run the file from the build folder instead of running the src folder version.

└── server/
    ├── src/
    │   └── file.ts
    └── build/
        └── file.js

If my open file is the src/file.ts, running the following launch.json config will run the build/file.js instead. But if I delete the build folder, then it will run the src/file.ts correctly.

doesn't this use the file in the currently active/focused editor tab? just focus the one you want. — starball
– starball ♦, Commented Nov 10 at 11:43
@starball that's the exact issue, I am focused on the file from src folder and it still runs the one in build folder — eliezra236
– eliezra236, Commented Nov 10 at 12:21
how do you know it's running the one from the build folder? can you give us readers some hard facts to help us see what you're seeing? — starball
– starball ♦, Commented Nov 10 at 12:35
@starball when the program starts from launch.json the first line logs the command that is running, and it literally says build/file.js — eliezra236
– eliezra236, Commented Nov 10 at 12:43
@eliezra236 do you have the rest of the launch.json by chance? You could hardcode the path as well as a troubleshooting step! I wonder if the issue comes from either another portion of your launch JSON or the definition of ${file} instead of ${workspaceFolder}. If the hardcoded path work, you may try something along the lines of "program": "${workspaceFolder}/server/src/file.tsx" — Henrique Donati
– Henrique Donati, Commented Nov 10 at 20:12

Atib Ur Rehman · Accepted Answer · 2025-11-11 23:26:02Z

0

Actually node resolves .js modules first like if .js exist use it, you can try using "runtimeArgs": ["--no-file-system-resolution"] in your launch.json:

{  
    "type": "node",  
    "request": "launch",  
    "name": "Server - Current File",  
    "program": "${file}",  
    "cwd": "${workspaceFolder}/server",  
    "runtimeExecutable": "tsx",  
    "runtimeArgs": \["--no-file-system-resolution"\],  
    "env": {  
        "NODE_ENV": "development"  
    }  
}

answered Nov 11 at 23:26

Atib Ur Rehman

1309 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

eliezra236 Nov 12 at 11:04

The reference to build folder happen from VSCode itself, so adding this arg will cause tsx --no-file-system-resolution ./build/file.js, so it will still refer to the build folder

Atib Ur Rehman Nov 12 at 16:00

you tried this solution? from Henrique Donati : "program": "${workspaceFolder}/server/src/file.tsx"

Collectives™ on Stack Overflow

How to disable VSCode launch.json prioritize build folder

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related