karma-runner / karma-coverage

A Karma plugin. Generate code coverage.
MIT License
767 stars 247 forks source link

karma coverage install error #168

Open jbarros35 opened 9 years ago

jbarros35 commented 9 years ago

I cannot install karma coverage

npm WARN package.json Dependency 'requirejs' exists in both dependencies and dev Dependencies, using 'requirejs@^2.1.18' from dependencies npm WARN engine coffee-script-redux@2.0.0-beta4: wanted: {"node":"0.6.x || 0.8.x "} (current: {"node":"0.12.4","npm":"2.10.1"}) npm ERR! Windows_NT 6.1.7601 npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs \node_modules\npm\bin\npm-cli.js" "install" npm ERR! node v0.12.4 npm ERR! npm v2.10.1 npm ERR! path C:\Users\jose\node\heroku\desolate-taiga-1397\node_modules\phantom js\bin\phantomjs npm ERR! code ENOENT npm ERR! errno -4058

npm ERR! enoent ENOENT, chmod 'C:\Users\jose\node\heroku\desolate-taiga-1397\nod e_modules\phantomjs\bin\phantomjs' npm ERR! enoent This is most likely not a problem with npm itself npm ERR! enoent and is related to npm not being able to find a file. npm ERR! enoent

npm ERR! Please include the following file with any support request: npm ERR! C:\Users\jose\node\heroku\desolate-taiga-1397\npm-debug.log

{ "name": "sharelinks", "version": "0.0.1", "private": true, "scripts": { "start": "node ./bin/www" }, "dependencies": { "body-parser": "~1.12.4", "cookie-parser": "~1.3.5", "crypto-js": "^3.1.5", "debug": "~2.2.0", "express": "~4.12.4", "jade": "~1.9.2", "jsonwebtoken": "^5.0.2", "morgan": "~1.5.3", "pg": "^4.4.0", "pg-hstore": "^2.3.2", "requirejs": "^2.1.18", "sequelize": "^3.2.0", "serve-favicon": "~2.2.1" }, "devDependencies": { "chai": "^1.9.1", "grunt": "^0.4.5", "grunt-contrib-jshint": "^0.10.0", "grunt-karma": "^0.8.3", "jasmine-core": "^2.3.4", "karma": ">=0.12.8", "karma-chai": "^0.1.0", "karma-jasmine": "^0.3.6", "karma-mocha": "^0.1.4", "karma-phantomjs-launcher": "^0.1.4", "load-grunt-tasks": "^0.6.0", "mocha": "^1.20.1", "requirejs": "^2.1.19" }

}

tried everything.

dignifiedquire commented 9 years ago

Sounds like an issue with npm and not with karma-coverage itself