So, I'm a user of the Atom editor on Windows, and trying to install any package (even packages that don't require native stuff and should not depend on gyp) get me an error message. On the Atom discussion site I was told that I might find help here. No matter what I try to install (apm install <any package name>), I get the following output:
Installing <package name> to C:\Users\jplatte\.atom\packages
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | win32 | ia32
gyp http GET https://atom.io/download/atom-shell/v0.22.0/node-v0.22.0.tar.gz
gyp WARN install got an error, rolling back install
gyp
I don't have any experience with npm or gyp, and it is very frustrating to still get the same error message after checking for the tenth time that I have everything installed that I should need. How do I debug this problem?
> Python 2.7 installed (C:Python27)
I'm not sure gyp likes 2.7. It should be fine..
Could you try installing node-gyp globally if it isn't already:
npm install -g node-gyp
Then go into that package's directory and run node-gyp rebuild --verbose?
Finally, I found the problem. Apparently the proxy settings are lost when https://atom.io/download/atom-shell/v0.22.0/node-v0.22.0.tar.gz redirects to another page. I have tried manually building packages, but the only package I'm aware of is that file, and when I ran gyp in there it complained about a missing bindings.gyp file. I still don't even know how gyp is used in all this, but to be honest, I don't care.
Anyway, this redirection + proxy problem wasn't found by me. There's a bug report about the issue I had on the apm repo (that I didn't find before because the error message I got was too vague). I don't know if anyone has actually filed a bug report here instead of just posting workarounds, so here's a link: https://github.com/atom/apm/issues/322
我真服
Most helpful comment
> Python 2.7 installed (C:Python27)I'm not sure gyp likes 2.7.It should be fine..Could you try installing
node-gypglobally if it isn't already:npm install -g node-gypThen go into that package's directory and run
node-gyp rebuild --verbose?