Closed justinwoo closed 4 years ago
Okay, I've successfully reproduced the bug on Linux:
And actually applied the fix manually the VSCode extension to test the fix:
It seems like the same fix does not apply to WSL2 VSCode so I will dig further into that myself, but it's unrelated to this bug.
I realized this probably needs to be done. I also realized that it seems like WSL2 might not pass env vars correctly, but I have to dig into this more.