Fatal error: EISDIR, illegal operation on a directory

Question

Fatal error: EISDIR, illegal operation on a directory

binarykitchen opened this issue 11 years ago · 16 comments

What does this error mean and how could it happen?

Answer 1 · 2013-11-02T12:24:33.000Z

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

Answer 2 · 2013-11-03T00:51:02.000Z

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?

Answer 3 · 2013-11-03T07:40:31.000Z

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

Answer 4 · 2013-11-03T09:43:49.000Z

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

Answer 5 · 2013-11-03T09:53:05.000Z

@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

Answer 6 · 2013-11-03T18:28:50.000Z

@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

Answer 7 · 2013-11-03T22:51:59.000Z

Sweet, thx guys

Answer 8 · 2013-11-04T08:52:54.000Z

@binarykitchen Thank you for reporting

Answer 9 · 2015-07-16T12:39:38.000Z

it's still happening

Answer 10 · 2015-08-05T17:26:24.000Z

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

Answer 11 · 2015-08-05T18:42:16.000Z

Anything special about the directory it fails on?

Answer 12 · 2015-08-07T15:46:38.000Z

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).

Answer 13 · 2016-02-15T21:55:14.000Z

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....

Answer 14 · 2016-03-15T11:00:30.000Z

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..

Answer 15 · 2016-12-02T22:06:28.000Z

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.

Answer 16 · 2018-03-29T16:36:04.000Z

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