Evaluate launch.json variables on the thin client side

[mattnotmitt]

I'm not exactly sure if this is where this should happen, but I like to keep a single Chrome profile for all debugging so I can have my react devtools installed. I've currently got my userDataDir set to
"userDataDir": "C:\\Users\\mcoomber\\chrome-vscode-debug",
which works great, but I'd love for it to be user agnostic so if another dev comes along to the project it will create a Chrome data dir in the right place. As such, I've tried setting it to
"userDataDir": "${env:HOMEDRIVE}${env:HOMEPATH}\\chrome-vscode-debug", which works fine as long as I'm not developing over remote ssh. Is there any way that this side of the chrome debugger can evaluate the environment variables rather than the remote client?

[connor4312]

Thanks for the issue, this is a functional dupe of microsoft/vscode-js-debug#591