Unhandled 'error' EISDIR

[zajca]

I getting this error on project and don't know why.

info download https://github.com/twbs/bootstrap/archive/v3.3.2.tar.gz into bootstrap
info cache https://github.com/FortAwesome/Font-Awesome/archive/v4.2.0.tar.gz into FontAwesome
info cache https://github.com/madebysource/lesshat/archive/v3.0.2.tar.gz into lesshat
info cache https://github.com/daneden/animate.css/archive/v3.1.0.tar.gz into animate.css
info cache https://github.com/scottjehl/picturefill/archive/2.2.0.tar.gz into picturefill
info cache https://github.com/ded/script.js/archive/v2.5.7.tar.gz into script
info cache git://github.com/kenwheeler/slick into slick
info cache git://github.com/lokesh/lightbox2 into lightbox2

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: EISDIR, read

this is what i have in package.json

  "napa": {
    "bootstrap": "twbs/bootstrap#v3.3.2",
    "FontAwesome": "FortAwesome/Font-Awesome#v4.2.0",
    "lesshat": "madebysource/lesshat#v3.0.2",
    "animate.css": "daneden/animate.css#v3.1.0",
    "picturefill": "scottjehl/picturefill#2.2.0",
    "script": "ded/script.js#v2.5.7",
    "requestAnimationFrame": "darius/requestAnimationFrame",
    "angularUtils": "michaelbromley/angularUtils",
    "slick": "kenwheeler/slick",
    "xhr": "LuvDaSun/xhr-polyfill",
    "lightbox2": "lokesh/lightbox2"
  },

[caseyWebb]

What version of npm are you experiencing this on?

[zajca]

Well it should be.

$ node -v
v0.10.29
$ npm -v
1.4.21

I deleted some repos and it's starts to work, but it's magic.

[tomek-he-him]

Have you tried updating npm? It’s at v3.3 nowadays.

It doesn’t look like it shouldn’t work on node v0.10 (no engines field).

[zajca]

What's the relation between napa and npm, how is napa depending on npm version?

[tomek-he-him]

napa uses the same dependencies as npm – but as far as I know they’re local and they don’t have anything to do with the global npm.

The important thing is how napa constructs the package.json and where it saves the dependencies after installing. That’s later interpreted by the global npm. See #45 – that was such a problem.

But you’re right – that doesn’t seem to have anything to do with your problem.

[tomek-he-him]

I meant https://github.com/shama/napa/issues/30.

[tomek-he-him]

@caseyWebb I’m not as deep in the topic as you are. Haven’t I messed something up?

[caseyWebb]

I garner that somehow your your local node_modules file system got corrupted, so simply deleting and reinstalling will solve your problem.

I notice you're running quite old versions of node and npm. Node is currently at 4.1.x, and npm 3.3.x.

You can use nvm or n to easily change your node version (I prefer n), and run npm install -g npm@3 to update npm globally.

Try those, and if you're still able to reproduce the issue, feel free to reopen, but I'm closing for now.

[tomek-he-him]

Link: https://github.com/tj/n. I wasn’t aware of n – thanks @caseyWebb!