Don't set HOME environment variable

[nagilson]

On Activation our Extension sets the HOME variable causing Git to no longer function.

Resolves #1795
Resolves #1400
Resolves #1686
Resolves #1707
Resolves #1916

This import statement in our code on WebRequestWorker.ts sets HOME.

const get_proxy_settings_1 = require("get-proxy-settings");

How do I know? I used the SysInternals Process Explorer to read the environment for every vscode sub process and went through the decompiled JS line by line in a binary search to see which line of code causes HOME to change 🥱

HOME is no longer changed.

This is definitely one of the weirdest bugs Ive had to solve.... seriously. We checked the source code this library and they dont edit HOME either, probably their 1 of dependencies does. But it doesn't really matter.

[pbl-pw]

I searched the node_modules directory and found that npm-conf was writing the HOME environment variable.

[dpalmetzvbg]

Thanks for investing your time and fixing it. Seems it was a difficult one... :-)

[nagilson]

Thanks for reporting it :) and @pbl-pw for helping as well with the detailed report. It was more confusing/weird and time-consuming than it was difficult... I would not expect a library import to do this 🙄 '
I will probably write a bug report over on their side

[nagilson]

There has been an issue on their repo since 2018 kevva/npm-conf#13 💀 Yes it is npm-conf