Allow remoteRoot also for node "Launch" action (for custom launchers) #11681

• VSCode Version: 1.4.0
• OS Version: Windows 10 x64 Anniversary

I have a feature request. I'm currently trying to get VSCode to debug node running in WSL, but I'd like to be able to use the "Launch" action also to launch node in WSL with the given settings.

I created a custom "wsl_node.exe" file (and set it as "runtimeExecutable") which launches bash with -c, calling a script, and passing a filtered view of environment variables and the current directory as well as the command line arguments. Then, my script changes the directory in bash to the /mnt-equivalent of the original current directory, sets the environment variables and runs node inside WSL with the given arguments, passing through its output and exit code.

This works so far, except for the fact that I have to use "externalConsole", otherwise I only get an error 0x80070057. I am able to use "debugger;" or "stopOnEntry", and then I can debug. However, the breakpoints and the project tree don't work right, because VSCode gets the path as "/mnt/c/xyz" instead of "C:\xyz".

I saw there is a "remoteRoot" which solves this problem, but it appears like it works only when attaching, not when launching... Is there any way I could solve this, or support for it could be added? I assume, though, that not many people will use this feature alone, so maybe support for a better integration with node running inside WSL could be helpful...