Closed basti1302 closed 9 years ago
process.ENOENT was removed, I think somewhere around node 0.4 or so. Setting error.errno = process.ENOENT actually sets the errno to undefined on all but very ancient node versions. This makes it impossible to check for the actual error reason.
error.errno = process.ENOENT
errno
Researching I actually found some discussions on an old connect issue where you participated that talk about this: https://github.com/senchalabs/connect/issues/119 :-)
Closing this due to lack of interest (mainly to get it out of my list of open pull requests)
process.ENOENT was removed, I think somewhere around node 0.4 or so. Setting
error.errno = process.ENOENT
actually sets theerrno
to undefined on all but very ancient node versions. This makes it impossible to check for the actual error reason.Researching I actually found some discussions on an old connect issue where you participated that talk about this: https://github.com/senchalabs/connect/issues/119 :-)