Fatal error: EISDIR, illegal operation on a directory

[binarykitchen]

What does this error mean and how could it happen?

[eoftedal]

Seems it's trying to read a directory as a file, from what I can find online about that error.

[binarykitchen]

Yeah but the problem is, it does not say which directory. Even when I enable --verbose, there is no hint at all which directory. Do you think you could wrap the code in a try-catch block and add more debug output for the verbose mode?

[eoftedal]

@binarykitchen Would you mind trying the new version, and see if that helps?

[phun-ky]

@binarykitchen what OS are you running? Node version? Npm version?

[binarykitchen]

@eoftedal Ah, with your latest version 0.1.12 I do not have that error anymore. All good now. What did you change?

@phun-ky OS X 10.9 and this:

$ node -v
v0.10.21
$ npm -v
1.3.11

[eoftedal]

@binarykitchen It now checks whether or not a path is a file before trying to open it. I think the former version would fail if a directory was named .js

[binarykitchen]

Sweet, thx guys

[eoftedal]

@binarykitchen Thank you for reporting

[yinrong]

it's still happening

[SaitejaP]

Yeah! I am facing this error too. I followed http://paularmstrong.github.io/swig/docs/tags/#include

[eoftedal]

Anything special about the directory it fails on?

[SaitejaP]

I am extremely sorry. I thought to post it in one repo but by mistake,
unintentionally posted here. Please remove my post or let me know how can I
remove it myself.
On 06-Aug-2015 12:12 am, "Erlend Oftedal" notifications@github.com wrote:

Anything special about the directory it fails on?

—
Reply to this email directly or view it on GitHub
#2 (comment).

[FrankV01]

For what it's worth, I received the error message when spaces were in my path... Quoting the path fixed the error. Not sure if this is others' issue but it's worth trying....

[eladcandroid]

It was happend for me too.. I just saw that package.json referenced to a package in a relative directory that doesn't exist and fixed it..

[mikepsinn]

I got this error when there was a symlink in the file path that I was copying from. One I removed the symlink, it worked.

[yacxn]

Strange I'm still getting this error two years later!