Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

npm not installing #7378

Closed
simran28693 opened this issue Feb 18, 2015 · 9 comments
Closed

npm not installing #7378

simran28693 opened this issue Feb 18, 2015 · 9 comments

Comments

@simran28693
Copy link

npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'install',
1 verbose cli   '-g' ]
2 info using npm@2.5.1
3 info using node@v0.12.0
4 verbose node symlink C:\Program Files\nodejs\\node.exe
5 silly cache add args [ '.', null ]
6 verbose cache add spec .
7 silly cache add parsed spec { raw: '.',
7 silly cache add   scope: null,
7 silly cache add   name: null,
7 silly cache add   rawSpec: '.',
7 silly cache add   spec: 'C:\\Users\\bagga',
7 silly cache add   type: 'local' }
8 error addLocal Could not install C:\Users\bagga
9 verbose stack Error: EISDIR, read
9 verbose stack     at Error (native)
10 verbose cwd C:\Users\bagga
11 error Windows_NT 6.1.7600
12 error argv "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g"
13 error node v0.12.0
14 error npm  v2.5.1
15 error code EISDIR
16 error errno -4068
17 error EISDIR, read
18 error If you need help, you may report this error at:
18 error     <http://github.com/npm/npm/issues>
19 verbose exit [ -4068, true ]
@kenany
Copy link
Contributor

kenany commented Feb 18, 2015

8 error addLocal Could not install C:\Users\bagga

You are trying to install something that's in your user directory?

@Cybercraft
Copy link

Same error but different way :

5046 verbose unlock done using C:\Users\Cybercraft\AppData\Roaming\npm-cache\_locks\npm-229c914b77731b40.lock for H:\node\node_modules\npm
5047 verbose stack Error: EISDIR, open 'H:\node\npm'
5047 verbose stack     at Error (native)
5048 verbose cwd H:\node\npm
5049 error Windows_NT 6.3.9600
5050 error argv "node" "H:\\node\\npm\\cli.js" "install" "npm" "-g"
5051 error node v0.12.0
5052 error npm  v2.6.0
5053 error path H:\node\npm
5054 error code EISDIR
5055 error errno -4068
5056 error EISDIR, open 'H:\node\npm'
5057 error If you need help, you may report this error at:
5057 error     <http://github.com/npm/npm/issues>
5058 verbose exit [ -4068, true ]

@othiym23
Copy link
Contributor

@simran28693 -g is the flat that tells npm to install a script globally, so if you want to run npm install -g, you have to tell it which package you want to install globally. The error message is maybe not the most helpful one in the world, but npm is treating your home directory as the source of the package to install globally because you omitted a package name, and is failing.

@Cybercraft You are getting a different error, and I'm not quite sure how it's happening. Can you upload all of npm-debug.log as a gist and include a link here? Something is trying to overwrite the npm directory under H:\node as a link or a file and failing, and I'd like to see if I can figure out how your configuration got into that state.

@simran28693
Copy link
Author

Thank you guys .... Get It :)

@Cybercraft
Copy link

@othiym23 Pastebin for npm-debug.log file content - http://pastebin.com/Y3wftTqU
Thanks

@jmgbsas
Copy link

jmgbsas commented Apr 30, 2015

I have similar error, only I need to install a package locally in windows
npm install underscore
and I am in my path local
almost I saw the problem I believe (I just start with javascript and node)
1 verbose cli [ 'C:\nodejs\node.exe', <---- we have 3 slash \ and shoul be 2
I am trying to use path.normalize but I can not found where do it in npm-cli.js
Thanks

0 info it worked if it ends with ok
1 verbose cli [ 'C:\nodejs\node.exe', <======== bad
1 verbose cli 'C:\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'underscore' ]
2 info using npm@2.7.4
3 info using node@v0.12.2
4 verbose node symlink C:\nodejs\node.exe
5 verbose stack Error: EISDIR, read
5 verbose stack at Error (native)
6 verbose cwd C:\nodejs\ConsoleWork\Beginig\chapter4\npm\jose
7 error Windows_NT 6.1.7601
8 error argv "C:\nodejs\node.exe" "C:\nodejs\node_modules\npm\bin\npm-cli.js" "install" "underscore"
9 error node v0.12.2
10 error npm v2.7.4
11 error code EISDIR
12 error errno -4068
13 error EISDIR, read
14 error If you need help, you may report this error at:
14 error https://github.com/npm/npm/issues
15 verbose exit [ -4068, true ]

Regards
Jose

@jmgbsas
Copy link

jmgbsas commented Apr 30, 2015

I observe that when i do copy paste in this box write comment the edition is deleting one slash
in that way my log is changed!
I had 3 slash and set 2 slash an so on.....
is bad this box write edition ???
Thanks
Jose

@JasmiRathod
Copy link

here is my npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm@2.12.1
3 info using node@v4.4.5
4 verbose stack Error: ENOENT: no such file or directory, open 'C:\xampp\htdocs\package.json'
4 verbose stack at Error (native)
5 verbose cwd C:\xampp\htdocs\reactApp
6 error Windows_NT 6.1.7601
7 error argv "C:\Program Files\nodejs\node.exe" "C:\Users\Admin\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "start"
8 error node v4.4.5
9 error npm v2.12.1
10 error path C:\xampp\htdocs\package.json
11 error code ENOENT
12 error errno -4058
13 error syscall open
14 error enoent ENOENT: no such file or directory, open 'C:\xampp\htdocs\package.json'
14 error enoent This is most likely not a problem with npm itself
14 error enoent and is related to npm not being able to find a file.
15 verbose exit [ -4058, true ]

help me on how to overcome this error

@npm-robot
Copy link

We're closing this issue as it has gone thirty days without activity. In our experience if an issue has gone thirty days without any activity then it's unlikely to be addressed. In the case of bug reports, often the underlying issue will be addressed but finding related issues is quite difficult and often incomplete.

If this was a bug report and it is still relevant then we encourage you to open it again as a new issue. If this was a feature request then you should feel free to open it again, or even better open a PR.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants