pump.io install fails #5701

Closed
sebastienkb opened this Issue Jul 15, 2014 · 6 comments

Comments

Projects
None yet
4 participants

Hi,

I'm new with nodejs and open source projects in general. Lately I have tried installing pump.io by following the instructions on http://pump.io/ but the install fails, complaining about an invalid character.
I tried maybe checking the said folder but by that time it is already deleted by the installer.
Is there a way for me to fix this myself? it is said to happen in a file called bcrypt_lib.vcxproj

I also tried downloading the latest ZIP version and npm install in the folder but this leads to the same error.

Alternatives to pump.io are welcome, the idea here is to create a proof of concept on social media modules.

Sorry for the poor paste.

C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules>npm install -g pump.io
\


> bcrypt@0.7.8 install C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules
\bcrypt
> node-gyp rebuild

|
C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\bcrypt>node "C:\DEV\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\bcrypt\build\bcrypt_lib.vcxproj(47,47): error MSB4025: The project file could not be loaded. Invalid character in the given encoding. Line 47, position 47.
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\MSBuild\12.0\bin\msbuild.exe` failed with exit code: 1

gyp ERR! stack     at ChildProcess.onExit (C:\DEV\nodejs\node_modules\npm\node_modules\node-gyp\lib\
build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:809:12)
gyp ERR! System Windows_NT 6.2.9200
gyp ERR! command "node" "C:\\DEV\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\bcrypt
gyp ERR! node -v v0.10.29
gyp ERR! node-gyp -v v0.13.1
gyp ERR! not ok
npm ERR! Error: ENOENT, chmod 'C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node
_modules\databank\node_modules\vows\.travis.yml'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\DEV\\nodejs\\\\node.exe" "C:\\DEV\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
 "install" "-g" "pump.io"
npm ERR! cwd C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\databank
\node_modules\vows\.travis.yml
npm ERR! fstream_path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\
databank\node_modules\vows\.travis.yml
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! fstream_finish_call chmod
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack C:\DEV\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:305:19
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, chmod 'C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\emailjs\node_modules\moment\lang\en-gb.js'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\DEV\\nodejs\\\\node.exe" "C:\\DEV\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
 "install" "-g" "pump.io"
npm ERR! cwd C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\emailjs\
node_modules\moment\lang\en-gb.js
npm ERR! fstream_path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\
emailjs\node_modules\moment\lang\en-gb.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! fstream_finish_call chmod
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack C:\DEV\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:305:19
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat 'C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node
_modules\connect-auth\examples\public\rssfeed.gif'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\DEV\\nodejs\\\\node.exe" "C:\\DEV\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
 "install" "-g" "pump.io"
npm ERR! cwd C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\connect-
auth\examples\public\rssfeed.gif
npm ERR! fstream_path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\
connect-auth\examples\public\rssfeed.gif
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack C:\DEV\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! error rolling back Error: EPERM, unlink 'C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_m
odules\pump.io\node_modules\underscore-contrib\docs\docco.css'
npm ERR! error rolling back  pump.io@0.3.0 { [Error: EPERM, unlink 'C:\Users\Sébastien Kalb\AppData\
Roaming\npm\node_modules\pump.io\node_modules\underscore-contrib\docs\docco.css']
npm ERR! error rolling back   errno: 50,
npm ERR! error rolling back   code: 'EPERM',
npm ERR! error rolling back   path: 'C:\\Users\\Sébastien Kalb\\AppData\\Roaming\\npm\\node_modules\
\pump.io\\node_modules\\underscore-contrib\\docs\\docco.css' }
npm ERR! bcrypt@0.7.8 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bcrypt@0.7.8 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.2.9200
npm ERR! command "C:\\DEV\\nodejs\\\\node.exe" "C:\\DEV\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
 "install" "-g" "pump.io"
npm ERR! cwd C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! code ELIFECYCLE
npm ERR! Error: ENOENT, lstat 'C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node
_modules\bunyan\node_modules\dtrace-provider\libusdt\test_usdt.c'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\DEV\\nodejs\\\\node.exe" "C:\\DEV\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
 "install" "-g" "pump.io"
npm ERR! cwd C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\bunyan\n
ode_modules\dtrace-provider\libusdt\test_usdt.c
npm ERR! fstream_path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\
bunyan\node_modules\dtrace-provider\libusdt\test_usdt.c
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack C:\DEV\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat 'C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node
_modules\underscore-contrib\docs\docco.css'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\DEV\\nodejs\\\\node.exe" "C:\\DEV\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
 "install" "-g" "pump.io"
npm ERR! cwd C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\undersco
re-contrib\docs\docco.css
npm ERR! fstream_path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\
underscore-contrib\docs\docco.css
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack C:\DEV\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat 'C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node
_modules\webfinger\node_modules\xml2js\src\xml2js.coffee'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\DEV\\nodejs\\\\node.exe" "C:\\DEV\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
 "install" "-g" "pump.io"
npm ERR! cwd C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\webfinge
r\node_modules\xml2js\src\xml2js.coffee
npm ERR! fstream_path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\
webfinger\node_modules\xml2js\src\xml2js.coffee
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack C:\DEV\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat 'C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node
_modules\showdown\test\cases\strong.html'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\DEV\\nodejs\\\\node.exe" "C:\\DEV\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
 "install" "-g" "pump.io"
npm ERR! cwd C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\showdown
\test\cases\strong.html
npm ERR! fstream_path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\
showdown\test\cases\strong.html
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack C:\DEV\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat 'C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node
_modules\sockjs\node_modules\faye-websocket\node_modules\websocket-driver\lib\websocket\driver\clien
t.js'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\DEV\\nodejs\\\\node.exe" "C:\\DEV\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
 "install" "-g" "pump.io"
npm ERR! cwd C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\sockjs\n
ode_modules\faye-websocket\node_modules\websocket-driver\lib\websocket\driver\client.js
npm ERR! fstream_path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\
sockjs\node_modules\faye-websocket\node_modules\websocket-driver\lib\websocket\driver\client.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack C:\DEV\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat 'C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node
_modules\emailjs\node_modules\mimelib\node_modules\encoding\node_modules\iconv-lite\encodings\tables
\cp950.json'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\\DEV\\nodejs\\\\node.exe" "C:\\DEV\\nodejs\\node_modules\\npm\\bin\\npm-cli.js"
 "install" "-g" "pump.io"
npm ERR! cwd C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\emailjs\
node_modules\mimelib\node_modules\encoding\node_modules\iconv-lite\encodings\tables\cp950.json
npm ERR! fstream_path C:\Users\Sébastien Kalb\AppData\Roaming\npm\node_modules\pump.io\node_modules\
emailjs\node_modules\mimelib\node_modules\encoding\node_modules\iconv-lite\encodings\tables\cp950.js
on
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack C:\DEV\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules\npm-debu
g.log
npm ERR! not ok code 0

C:\Users\Sébastien Kalb\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules>
Member

faiq commented Jul 15, 2014

Hey! I would first suggest bumping up your version number of npm and trying the install again

npm install -g npm@1.4.20

There were a lot of fixes, and this might help any problem you have.

If you're still having a problem, let us know and I'll try to help you further :)

Hi faiqyou and thanks for your time.

I did what you said but

npm --version

still returns 1.4.14

does it mean that the install failed or the version number wasn't updated?
I tried running my npm install anyway (both with -g and without -g in a local node_modules folder) but no avail. This time, though, the output is slightly different, yet still complaining about the crypt package.

Should I uninstall npm and reinstall it, would that help?
Do consecutire attempts overwrite or ignore previous installs?

Thanks


[edit: deleted because next post fixes this partially]

Note: I downloaded npm 1.4.21 from zip source and installed in my dev folder (C:\DEV\nodejs\node_modules)
npm --version shows 1.4.21 now
so that part is solved, but many other errors show now.
Looks like a bunch of C headers are missing, node-gyp is missing or outdated. is there anything I can do to fix that part?


D:\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules>npm install pump.io
\

bcrypt@0.7.8 install D:\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules\pump.io\node_module
s\bcrypt
node-gyp rebuild

D:\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules\pump.io\node_modules\bcrypt>node "C:\DEV\n
odejs\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m"
switch.
blowfish.cc
bcrypt.cc
bcrypt_node.cc
c:\users\seb.node-gyp\0.10.29\deps\uv\include\uv-private/uv-win.h(32): fatal error C1083: Cannot o
pen include file: 'winsock2.h': No such file or directory (..\src\bcrypt_node.cc) [D:\Dropbox\works
pace-nodejs\BTwitter-pump.io\node_modules\pump.io\node_modules\bcrypt\build\bcrypt_lib.vcxproj]
..\src\bcrypt.cc(232): warning C4267: '=' : conversion from 'size_t' to 'unsigned char', possible l
oss of data [D:\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules\pump.io\node_modules\bcrypt
build\bcrypt_lib.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\12.0\bin\msbuild.exe failed with exit code: 1

gyp ERR! stack at ChildProcess.onExit (C:\DEV\nodejs\node_modules\npm\node_modules\node-gyp\lib
build.js:267:23)
gyp ERR! stack at ChildProcess.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:809:12)
gyp ERR! System Windows_NT 6.2.9200
gyp ERR! command "node" "C:\DEV\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.j
s" "rebuild"
gyp ERR! cwd D:\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules\pump.io\node_modules\bcrypt
gyp ERR! node -v v0.10.29
gyp ERR! node-gyp -v v0.13.1
gyp ERR! not ok
npm WARN engine connect@2.0.0: wanted: {"node":">= 0.5.0 < 0.7.0"} (current: {"node":"0.10.29","npm"
:"1.4.21"})

dtrace-provider@0.2.4 install D:\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules\pump.io\no
de_modules\bunyan\node_modules\dtrace-provider
node-gyp rebuild

D:\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules\pump.io\node_modules\bunyan\node_modules\d
trace-provider>node "C:\DEV\nodejs\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bi
n\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m"
switch.
npm ERR! bcrypt@0.7.8 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bcrypt@0.7.8 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.2.9200
npm ERR! command "C:\DEV\nodejs\node.exe" "C:\DEV\nodejs\node_modules\npm\bin\npm-cli.js"
"install" "pump.io"
npm ERR! cwd D:\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! D:\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules\npm-debug.log
npm ERR! not ok code 0

D:\Dropbox\workspace-nodejs\BTwitter-pump.io\node_modules>

Member

faiq commented Jul 17, 2014

im glad you were able to upgrade! This node gyp error seems pretty weird, and it might actually
be a problem with the bcrypt package. Figure out what version number of bcrypt you're trying to install , by looking at your package.json. Then, inside your node_modules directory try the following command

npm install bcrypt@versionnumber 

I really hope this works.

@othiym23 othiym23 added the support label Sep 18, 2014

Contributor

smikes commented Jan 28, 2015

Is this still a problem for you?

I wonder if the problem could be triggered by the "é" character in your user name. Could you try isolating that by running the installation in a directory that contains only ASCII characters such as C:\WINDOWS\TEMP?

If that is the problem, then we will need your help to track down the bug between npm, node-gyp and (less likely) Python or Visual Studio. It's possible that one program expects utf-8 and another is generating latin-1 or some incompatible encoding.

You should also update npm if possible; to update npm on Windows, follow the instructions here: https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows

We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and open a new issue!)

Thanks!

Contributor

othiym23 commented Feb 20, 2015

Closing as abandoned.

@othiym23 othiym23 closed this Feb 20, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment