win 64 npm install issue

[cooolbasha]

hi,
i am problem installing

c:\wed\node_modules\bcrypt>node "C:\Program Files\nodejs\node_modules\npm\bin\no
de-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
gyp ERR! build error
gyp ERR! stack Error: ENOENT, open 'C:\Users\Administrator.node-gyp\0.8.11\x64
node.lib'
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\Program Files\nodejs\node_modules\npm\node_modu
les\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd c:\wed\node_modules\bcrypt
gyp ERR! node -v v0.8.11
gyp ERR! node-gyp -v v0.6.11
gyp ERR! not ok
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! cmd "/c" "node-gyp rebuild" failed with 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the bcrypt 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 bcrypt
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nod
ejs\node_modules\npm\bin\npm-cli.js" "install" "bcrypt"
npm ERR! cwd c:\wed
npm ERR! node -v v0.8.11
npm ERR! npm -v 1.1.62
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! c:\wed\npm-debug.log
npm ERR! not ok code 0

the

[mscdex]

Can you upgrade your version of node and try again (at least v0.8.22 if really need to stick with v0.8.x, otherwise v0.10.x)?

[DrYSG]

I am running 0.10.13.0 and getting issue #296

I don't know if that is related to this issue, other than it is also a win7 64-bit machine.

[ghost]

I am running node 0.10.13.0 as well and have the same issues on win7 64 and 2008 64

[JayBeavers]

Please try and reproduce after installing a fixed node-gyp (npm install node-gyp -g; node-gyp clean; node-gyp configure; node-gyp build). Please install VS 2013 Express for Windows Desktop. Please run node/node-gyp from a Developers Command Prompt.

I believe this is all fixed and will work well on x64 with updated Visual Studio 2013 and updated node-gyp (still waiting for node 0.10.x to be updated, see nodejs/node-v0.x-archive#6667). Let me know if this is not the case.