[Issue]: nvm.exe hangs when started by TeamCity because Stdout is not a character mode device about nvm-windows HOT 3 CLOSED

That part I can't prove directly.

Wrote that over a bit of time, this isn't true. I added some debug output to the isTerminal() func that showed that stdout was a named pipe and not a char device - hence the fix that worked for me in the context of TeamCity.

from nvm-windows.

The isTerminal feature was added for an obscure use case, but has proven to be more hassle than it is worth. It will be pulled out in the next version (there's already a PR). Unfortunately, it will be a little while until I can release 1.1.13 because our code signing certificate got locked out (slow process to get it reinstated). For the time being, I'd recommend using 1.1.11.

from nvm-windows.

The isTerminal feature was added for an obscure use case, but has proven to be more hassle than it is worth. It will be pulled out in the next version (there's already a PR). Unfortunately, it will be a little while until I can release 1.1.13 because our code signing certificate got locked out (slow process to get it reinstated). For the time being, I'd recommend using 1.1.11.

Great! Thanks. I'm alright to continue using my compiled version for now.

from nvm-windows.