Error installing github repository: "ERR! EISDIR" #7232
Comments
There might be an ambiguity between the Try using the long form if you want to install from the github repo:
Please let me know if I am misunderstanding your question. |
I'm afraid I get the same error if I try to install the repo using a git url. |
/cc @othiym23 git dependency problems Can you try updating to
|
I just updated npm and still get the same output:
Huh! I wonder what insane thing I did to that repo to make it so uncooperative? Do you (or anyone) have any insight into the addLocal errors? Is there a potential permissions issue? |
@neagle Your issue is that you are trying to |
Ah, if that's the case I misunderstood the capacity of adding a github repo Nate Eagle On Jan 28, 2015, at 5:00 PM, Kenan Yildirim notifications@github.com @neagle https://github.com/neagle Your issue is that you are trying to npm — |
@kenany Thanks for seeing that! Next time I will remember to look at the repository in question. 🤦 |
Sorry to take your time, Sam! Nate Eagle On Jan 29, 2015, at 12:20 AM, Sam Mikes notifications@github.com wrote: @kenany https://github.com/KenanY Thanks for seeing that! Next time I — |
Same happened to me... I haven't realized I cannot point to just any Github repo |
This thread was extremely helpful, thanks for the clear-cut answer! |
@kenany - can the error message be updated to be more helpful? |
@recursify |
@kenany - I'm on |
Got the same error on |
I got EISDIR on npm 3.3.0. The issue was that the Git site didn't have a package.json, but that was not at all clear from EISDIR. An updated error message would be helpful. |
This thread was really helpful! Would it be possible to describe the possible problem in the error message? |
@kenany: |
@piggyslasher Like #9396? |
I'm fairly certain you used to be able to do this at some point, it was wildly useful. |
Took me a while to figure out what |
I'm having trouble installing a github repository with npm. I had this previously working on a different branch of the remote repo, so there's probably something in the repository itself that's causing the problem, but I'm having trouble finding any insight into what it might be. Is there anyone who might be able to help me out?
The text was updated successfully, but these errors were encountered: