-
Notifications
You must be signed in to change notification settings - Fork 3k
Error with npm install on v3.0.0 on windows #8701
Comments
Ok, so this is an interesting one. It's failing because it's checking for permissions to write to On 0.12 and io.js it uses a new API call for this (that's buggy in some io.js builds), but on 0.10 it actually just creates a file and sees if it succeeded. So it's entirely possible that I messed something up in my "create a file and check see if we succeeded" thing… But can you verify that you can create files in |
I am also running into a variant of this error as well I think. I even tried to downgrade npm to see if that fixes which (ironically) fails due to permission issues, to Jumping to node 0.12.5 didn't fix it, though maybe it was already in a bad state. In any case npm deleted itself when trying to downgrade when I tried to run it again in node 0.12.5. |
I just tried npm 3 again (after rolling back to npm 2 to get back to work), and this time I'm getting the same error but it's complaining about the directory I am running npm install inside of. I do have access to create files, and can do something like 'echo Hello > test.txt' from the same shell I'm running npm from and it has no problems. |
Several things If you disable the check e.g. see the added
to here https://github.com/npm/npm/blob/master/lib/install/check-permissions.js#L77 then npm seems to install fine. |
For 3.1.0 (this Thursday's release) I'm going to disable this check on Windows. I'll come back to it next week to find a real solution. |
I have a test branch for this, but it needs more marinating before it gets merged. NEXT WEEK! |
I believe this is fixed as of 3.1.3 but I'd love to have some of the folks who've experienced this verify that? |
Sorry, I'm not on 0.10.x any more |
I'm going to close this as resolved, but if you run into this issue again, I encourage you to open a new issue! |
I am looking forward to npm@3 as I have just run into the notorious 'nested node_modules lead to paths being too long on Windows' issue. I am currently trying this on a Win 8 install.
Running npm install seems to succeed in downloading the various modules and sub-modules of each module, and npm install --log-level silly shows an 'idealTree' that looks reasonable, however it ends up erroring out with what seems like a permissions issue. Specifically it reads: npm ERR! Error: EACCES, access 'C:\Users\john.arnold\AppData\Roaming\npm\node_modules\npm\node_modules'
This is odd because I have gone into that folder and added full permissions to 'Everyone'. I have also tried running this through an administrator console with the same results.
Here is the specific output:
(cutting out a lot of npm sill idealTree lines, and the initial adding of packages to the npm-cache)
The text was updated successfully, but these errors were encountered: