Hardcoded cmd PATH is never updated! about nvmw HOT 6 CLOSED

I installed nvmw years ago and forgot it did this. Now after days of searching the stackexchange for answers as to why my cmd path is out of wack I found the culprit.

from nvmw.

A qoute from the readme: You should install a system version Node with Windows installer.
Just saying ;) Correct me if I'm wrong but I think this means custom node installations are not supported under Windows.

from nvmw.

This means that I must install let's call it "root" nodejs version, where I install nvmw, and then switch (use) / install / uninstall other versions.. That's exactly what I've done. The problem is that it messes up with my PATH, so I cannot use it for anything else, nor I can uninstall nvmw, because it's in another folder of nodejs...

from nvmw.

Yes, I got you. The PATH variable in cmd_auto_start.bat is only updated by doing

  nvmw switch-deactivate
  nvmw switch SOME_VERSION

manually and the complete replacement of the PATH variable seems to be bad designed.

from nvmw.

If this module won't be updated I think it even has to be deleted - this is huge error and extremely dangerous to work with. Being able to modify your PATH is crucial! I'm sorry for all of you that spent numerous hours looking for the problem :)

from nvmw.

This has literally caused me to not be able to work with Qt Creator anymore for a year since the Windows Build Tools and the Win10 SDK binaries (mostly cl.exe and rc.exe) were always removed from the PATH variable (see my answer on SO).
I am incredibly pissed off but also happy to have finally figured it out.

from nvmw.