cant install through package manager

[lucidlips]

installing through package manager is failing.

"Installing “info-comment@0.1.1” failed.Show output…"

[ibykow]

Hi, do you mind pasting the output you get?
Also, what os/atom version are you on?
Thanks.

[Septh]

Hi,

Ran into the same problem. Using Atom 1.6.2 on Windows 7 SP1. Here's Atom output:

> runas@3.1.1 install T:\Windows\apm-install-dir-116311-21492-1winbsn\node_modules\info-comment\node_modules\text-buffer\node_modules\pathwatcher\node_modules\runas
> node-gyp rebuild

T:\Windows\apm-install-dir-116311-21492-1winbsn\node_modules\info-comment\node_modules\text-buffer\node_modules\pathwatcher\node_modules\runas>if not defined npm_config_node_gyp (node "C:\Users\Stephan\AppData\Local\atom\app-1.6.2\resources\app\apm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node  rebuild ) 

> marker-index@3.1.0 install T:\Windows\apm-install-dir-116311-21492-1winbsn\node_modules\info-comment\node_modules\text-buffer\node_modules\marker-index
> node-gyp rebuild

T:\Windows\apm-install-dir-116311-21492-1winbsn\node_modules\info-comment\node_modules\text-buffer\node_modules\marker-index>if not defined npm_config_node_gyp (node "C:\Users\Stephan\AppData\Local\atom\app-1.6.2\resources\app\apm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node  rebuild ) 

> oniguruma@5.1.2 install T:\Windows\apm-install-dir-116311-21492-1winbsn\node_modules\info-comment\node_modules\oniguruma
> node-gyp rebuild

T:\Windows\apm-install-dir-116311-21492-1winbsn\node_modules\info-comment\node_modules\oniguruma>if not defined npm_config_node_gyp (node "C:\Users\Stephan\AppData\Local\atom\app-1.6.2\resources\app\apm\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node  rebuild ) 

gypgypgypnpm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Users\\Stephan\\AppData\\Local\\atom\\app-1.6.2\\resources\\app\\apm\\bin\\node.exe" "C:\\Users\\Stephan\\AppData\\Local\\atom\\app-1.6.2\\resources\\app\\apm\\node_modules\\npm\\bin\\npm-cli.js" "--globalconfig" "C:\\Users\\Stephan\\.atom\\.apm\\.apmrc" "--userconfig" "C:\\Users\\Stephan\\.atom\\.apmrc" "install" "T:\\Windows\\d-116311-21492-11twq89\\package.tgz" "--target=0.34.5" "--arch=ia32"
npm ERR! node v0.10.40
npm ERR! npm  v2.13.3
npm ERR! code ELIFECYCLE

npm ERR! runas@3.1.1 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the runas@3.1.1 install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

[ibykow]

Thanks. I'll have a look at it on my windows pc in a bit.

[shahmalav]

Hi @ibykow, were you able to look at the issue? I am facing same problem.

[ibykow]

Hi, I've been able to replicate this issue on Win10 x64 , but it hasn't been consistent. When the error pops up, I tried installing/reinstalling the package and it would work.

Also, I haven't been able to replicate this error since installing Visual Studio community edition. It might have something to do with VS installing some necessary .NET dependencies, but that's just a guess.

Besides that, it looks to be a node-gyp problem of some sort. The info-comment plugin doesn't call node-gyp explicitly. Instead, node-gyp is used as part of Atom's package installation process.

A lot of people seem to be dealing with node-gyp/ node-gyp rebuild problems on windows. One of the more straight-forward solutions I've seen being recommended was to remove the C:\Users\USERNAME\.atom\.node-gyp folder.

Here are some of the links I've looked at so far:
emmetio/emmet-atom#32 (delete .node-gyp folder)
atom/atom#11710 (reinstall visual studio from ISO)
http://stackoverflow.com/questions/35293117/npm-install-that-requires-node-gyp-fails-on-windows (install .NET dependencies and reinstall python)

If you've been able to overcome this error with any of the suggestions above, let me know.
I'll keep this thread open for a while longer to see if we can get something working.