Attempting to install Angular using the NPM interface in VS 2013, however it consistently fails when attempting to install (or build?) Contextify, which I presume must be an Angular dependency.
Have tried using a couple of Node versions (0.10.23 and 0.10.22), and also the 64 and 32 bits.
I am using VS Ultimate 2013.
I can install Angular through the usual Node command line tool with no problem using the command 'npm install angular'.
Error shown here:
npm ERR! contextify@0.1.6 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the contextify@0.1.6 install script.
npm ERR! This is most likely a problem with the contextify 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 contextify
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files (x86)\\nodejs\\\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "angular" "--save"
npm ERR! cwd C:\Work\ExpressTest
npm ERR! node -v v0.10.23
npm ERR! npm -v 1.3.17
npm ERR! code ELIFECYCLE
Comments: Was there a npm-debug.log file that was written out? Over on Stack Overflow I see this issue: http://stackoverflow.com/questions/13899187/install-contextify-on-windows-7-error-gyp-failed-with-exit-code-2 which looks similar, but it has some additional error messages to might be completely different. On my Node install node-gyp is a dependency of npm already but if you have some additional error messages that match it you might want to try "npm install -g node-gyp" from the command line and see if that fixes the issue. I'm assuming that's the right path to your node install - we find npm by search the path for a location with npm.cmd and then end up invoking that (so you should also see a cmd.exe process running npm.cmd as well). Also, if you right click on the project node in VS and choose Open Command Prompt here and try doing the install do you get the same result? That should have the same set of env vars as when we run npm from within VS so that might help figure out what's going on.
Have tried using a couple of Node versions (0.10.23 and 0.10.22), and also the 64 and 32 bits.
I am using VS Ultimate 2013.
I can install Angular through the usual Node command line tool with no problem using the command 'npm install angular'.
Error shown here:
npm ERR! contextify@0.1.6 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the contextify@0.1.6 install script.
npm ERR! This is most likely a problem with the contextify 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 contextify
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files (x86)\\nodejs\\\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "angular" "--save"
npm ERR! cwd C:\Work\ExpressTest
npm ERR! node -v v0.10.23
npm ERR! npm -v 1.3.17
npm ERR! code ELIFECYCLE
Comments: Was there a npm-debug.log file that was written out? Over on Stack Overflow I see this issue: http://stackoverflow.com/questions/13899187/install-contextify-on-windows-7-error-gyp-failed-with-exit-code-2 which looks similar, but it has some additional error messages to might be completely different. On my Node install node-gyp is a dependency of npm already but if you have some additional error messages that match it you might want to try "npm install -g node-gyp" from the command line and see if that fixes the issue. I'm assuming that's the right path to your node install - we find npm by search the path for a location with npm.cmd and then end up invoking that (so you should also see a cmd.exe process running npm.cmd as well). Also, if you right click on the project node in VS and choose Open Command Prompt here and try doing the install do you get the same result? That should have the same set of env vars as when we run npm from within VS so that might help figure out what's going on.