ENOTCONN error after installing node-v0.10.9-x64.msi

[DanKaplanSES]

My issue is documented here: http://stackoverflow.com/questions/16879027/why-am-i-getting-errors-running-the-coffee-command-in-cygwin

After installing node-v0.10.9-x64.msi, when I run node it says:

$ node

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: read ENOTCONN
    at errnoException (net.js:884:11)
    at Socket._read (net.js:389:21)
    at Socket.Readable.read (_stream_readable.js:320:10)
    at Socket.read (net.js:291:43)
    at new Socket (net.js:185:10)
    at process.stdin (node.js:660:19)
    at startup (node.js:145:16)
    at node.js:901:3

I don't know anything about node.js so I apologize if I'm not giving enough information.

[DanKaplanSES]

I installed node-v0.11.2-x86.msi and still get this error.

[bnoordhuis]

You don't mention it explicitly but I assume you're running it from inside a cygwin shell? Does it work from a normal terminal window? (I guess the Windows nomenclature is 'command window'?)

[DanKaplanSES]

Yes, when I run it from the command window it says this:

C:\Users\foo>node
>

There's no error.

Now that I know that, I have found a way to build on cygwin here: https://github.com/joyent/node/wiki/Building-node.js-on-Cygwin-%28Windows%29

But I found comments on this question that imply I shouldn't have to do this: http://stackoverflow.com/questions/10043177/node-js-cygwin-not-supported

I'm not sure what is the right direction to take, or if this is even a bug. A commenter on SO mentioned that this issue might be related: github.com/remy/nodemon/issues/176

[bnoordhuis]

Cygwin itself hasn't been supported for a long time. As to running node in a cygwin shell, that's kind of a grey area.

/cc @piscisaureus You should chime in here.

[kenjiru]

I'm also getting this error on cygwin, after updating from node.js 0.8.x.

As it used to work before, I see this bug as a regression.

[jordwalke]

Is it asking too much to be able to run the non-cygwin node from a cygwin environment?

[bnoordhuis]

None of the people on the core team use cygwin. As far as priorities go, making it work is on the ultra low end of the scale. If running inside a cygwin shell is that important to you, I suggest you scratch your own itch.

[bnoordhuis]

I remember what the issue is, it's come up before. See this link for more detail. tl;dr A cygwin terminal is not a console, it's a pipe in disguise.

We won't go out of our way to accommodate that - node.js does reasonably advanced things with and to the console - but if someone comes up with a minimally invasive patch, we'll definitely consider it.

[zot]

Node works for me in a Cygwin shell if I run it in a windows command prompt (Cygwin.bat).