karma-runner / karma

Spectacular Test Runner for JavaScript
http://karma-runner.github.io
MIT License
11.95k stars 1.71k forks source link

Testacular installation issue with npm #46

Closed LeviLewis closed 12 years ago

LeviLewis commented 12 years ago

When I try to install testacular with the command: "npm -g install testacular", I get the following output:. I am runnning Windows 7 Professional and my Node version is 0.8.8

npm http GET https://registry.npmjs.org/testacular
npm http 304 https://registry.npmjs.org/testacular
npm http GET https://registry.npmjs.org/socket.io
npm http GET https://registry.npmjs.org/chokidar
npm http GET https://registry.npmjs.org/optimist
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/glob
npm http 304 https://registry.npmjs.org/chokidar
npm http 304 https://registry.npmjs.org/minimatch
npm http 304 https://registry.npmjs.org/optimist
npm http 304 https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/glob

> chokidar@0.4.0 postinstall C:\Users\clewis\AppData\Roaming\npm\node_modules\testacular\node_modules\chokidar
> node setup.js postinstall

The system cannot find the path specified.
npm http GET https://registry.npmjs.org/lru-cache
npm http GET https://registry.npmjs.org/graceful-fs
npm http GET https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/wordwrap
npm http GET https://registry.npmjs.org/socket.io-client/0.9.10
npm http GET https://registry.npmjs.org/policyfile/0.0.4
npm http GET https://registry.npmjs.org/redis/0.7.2
npm ERR! chokidar@0.4.0 postinstall: `node setup.js postinstall`
npm ERR! `cmd "/c" "node setup.js postinstall"` failed with 1
npm ERR!
npm ERR! Failed at the chokidar@0.4.0 postinstall script.
npm ERR! This is most likely a problem with the chokidar package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node setup.js postinstall
npm ERR! You can get their info via:
npm ERR!     npm owner ls chokidar
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\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "-g" "install" "testacul
ar"
npm ERR! cwd C:\Users\clewis
npm ERR! node -v v0.8.8
npm ERR! npm -v 1.1.59
npm ERR! code ELIFECYCLE
npm http 304 https://registry.npmjs.org/lru-cache
npm http 304 https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/wordwrap
npm http 304 https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/socket.io-client/0.9.10
npm http 304 https://registry.npmjs.org/redis/0.7.2
npm http GET https://registry.npmjs.org/hiredis
npm http GET https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http GET https://registry.npmjs.org/ws
npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/hiredis
npm WARN package.json hiredis@0.1.14 No README.md file found!

> hiredis@0.1.14 preinstall C:\Users\clewis\AppData\Roaming\npm\node_modules\testacular\node_modules\socket.io\node_modules\redis\node_modules\hi
redis
> make || gmake

The system cannot find the path specified.
'make' is not recognized as an internal or external command,
operable program or batch file.
'gmake' is not recognized as an internal or external command,
operable program or batch file.
npm WARN optional dep failed, continuing hiredis@0.1.14
npm http 304 https://registry.npmjs.org/uglify-js/1.2.5
npm http 304 https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/ws
npm http GET https://registry.npmjs.org/zeparser/0.0.5
npm http GET https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/tinycolor
npm http GET https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/zeparser/0.0.5
npm http 304 https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/tinycolor
npm http 304 https://registry.npmjs.org/options

> ws@0.4.21 install C:\Users\clewis\AppData\Roaming\npm\node_modules\testacular\node_modules\socket.io\node_modules\socket.io-client\node_modules
\ws
> node install.js

The system cannot find the path specified.
[ws v0.4.21] Attempting to compile blazing fast native extensions.
[ws v0.4.21] Native code compile failed (but the module will still work):
[ws v0.4.21] The native extensions are faster, but not required.
[ws v0.4.21] On Windows, native extensions require Visual Studio and Python.
[ws v0.4.21] On Unix, native extensions require Python, make and a C++ compiler.
[ws v0.4.21] Start npm with --ws:verbose to show compilation output (if any).
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Users\clewis\npm-debug.log
npm ERR! not ok code 0
vojtajina commented 12 years ago

Can you try to remove npm cache ? (~/npm-cache/*)

It looks like some problem in chokidar post install script (which is compiling coffeescript), however I just tried it on windows and seem to be working fine for me.

vojtajina commented 12 years ago

Closing this issue, please re-open, if you still experience it.

ffesseler commented 12 years ago

Hi, I experience the exact same issue with Win 7 Pro & node 0.8.9 Cleaning the npm-cache don't do anything

vojtajina commented 12 years ago

Please file an issue with Chokidar https://github.com/paulmillr/chokidar

ffesseler commented 12 years ago

FYI, I've been able to install testacular by removing my previous node 64 bits installation and installing a 32 bits version instead. Other workarounds (removing npm-cache, reinstalling node) didn't work for me.

ALeschinsky commented 11 years ago

I can't install testacular on my Win 7 desktop - both node.js 64 and 32 bits, cleared cache million times, nothing seems to help. Here's npm-debug.log I'm getting: http://pastebin.com/gQGUirRP

dignifiedquire commented 11 years ago

@ALeschinsky This is sadly again a problem by the great way chokidar is published. Do you have a local version of chokidar on that you are working? Which methods of cache clearing did you try?