Got errors on windows and centos about dev/tty

[adriengibrat]

I got this error using Inquirer.js since this morning

On centOS

Error: ENXIO, no such device or address '/dev/tty'

On windows

Error: ENOENT, no such file or directory 'c:\dev\tty'

Sorry, I don't have time for further investigation, but seems related to your project.

[rmg]

Looks like tty assumes there is a tty to attach to, but that's not always the case.

Sadly that means this module's promise of "Guaranteed read and write streams to the terminal" comes with the caveat that there must actually be a terminal of some kind :-/

[jonschlinkert]

we're getting this error in some of the enquirer prompt libs as well. but for OSX

edit: sorry to be clear the error was for OSX on travis, but I don't get the error locally on OSX for some reason.

[nagapavan]

Getting this error on OSX while using inside VSCode. From CLI, it works without a hitch.

[matthewjumpsoffbuildings]

i tried using this module to fix an issue i am having with visionmedia/node-progress#179 - the progress bar is not rendering when using git-bash.exe on windows, since it is not TTY. The /bin/bash.exe that is in the Git install folder is TTY and the progress bar works fine, as does regular old cmd.exe.

i attempted to use this library for its promise of guaranteed TTY output streams, but when i run it in git-bash.exe i get the node error

Error: ENOENT, no such file or directory '/dev/tty'

edit:
weird thing is, in git-bash, if i just type echo "hello" > /dev/tty it actually works - eg it logs out "hello" into the current console, so why is the fs attempt to open a stream to this failing?

[0x57e11a]

Damn this is old, still no fix for using Windows?

[wing1003]

I got the same error on OSX.

Error: ENXIO: no such device or address, open '/dev/tty'