69
votes

I used node.js to install karma. My first try failed when running the following command on Terminal:

npm install -g karma

That failed so I decided to use:

sudo npm install -g karma

After entering my password it seemed to install correctly. I am pasting part of the output of the install, maybe it will mean something to someone and it will be relevant to my question. After all the npm http messages this is what I see:

> [email protected] install /usr/local/share/npm/lib/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
  SOLINK_MODULE(target) Release/bufferutil.node: Finished
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/validation.node
  SOLINK_MODULE(target) Release/validation.node: Finished
/usr/local/share/npm/bin/karma -> /usr/local/share/npm/lib/node_modules/karma/bin/karma
[email protected] /usr/local/share/npm/lib/node_modules/karma
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected])
├── [email protected]
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected])
├── [email protected]
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected])

Then when I try to run the following command to create a karma config file with this command:

karma init karma.config.js

this is the message that gets returned:

-bash: karma: command not found

I have tried the same command with sudo before it but I get the same result.

Does anyone have any idea as to what is going on? Any help is appreciated.

*Update! I decided to check a file named: builderror.log located in: /usr/local/share/npm/lib/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws

This is what it shows:

gyp WARN EACCES user "root" does not have permission to access the dev dir "/Users/eperez/.node-gyp/0.10.5"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/share/npm/lib/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws/.node-gyp"
gyp http GET http://nodejs.org/dist/v0.10.5/node-v0.10.5.tar.gz
gyp http 200 http://nodejs.org/dist/v0.10.5/node-v0.10.5.tar.gz
9
it's apparently not in your path, confirm with which karma. i've experienced npm installing stuff to a not-in-path-by-default location, I think on Arch. i don't remember where it went though sorry :( ps you can do cd /; find|grep karma to get all filenames on system with karma in filename or pathPlato
I ran the command and this is what I got. Not sure what it means though: usage: find [-H | -L | -P] [-EXdsx] [-f path] path ... [expression] find [-H | -L | -P] [-EXdsx] -f path [path ...] [expression]iChido
OK sorry your find program behaves differently than mine. Anyway you will need to find where npm installed stuff and make sure that folder is added to your path for your terminal sessions. FWIW on my Linux Mint install, npm -g puts stuff in /usr/local/binPlato
I have the same issue. None of the suggestions/answers helped.Doug
The command line interface is in a separate package. To install this use: npm install -g karma-climayankcpdixit

9 Answers

250
votes

@mayankcpdixit gave the answer up there in a response to the OP's original question, but I'll put it here again in case anyone misses it.

You do not need to uninstall everything, and if I had to manually add a new path link for every npm package I try to install I'd probably shoot myself.

npm install -g karma-cli

Boom. Now you have karma command lines installed. Just like Grunt.


Edit: Please don't forget to upvote @mayankcpdixit as well, he commented directly on the original post, but didn't actually "answer" the question.

37
votes

In your ~/.bash_profile (or similar) amend your PATH to include npm-installed binaries:

export PATH="$PATH:/usr/local/share/npm/bin"

I had this very same issue, and found this solution to be less time-consuming and impactful than completely re-installing node.

EDIT this has also worked for others in bash_profile

export PATH="$PATH:/usr/local/lib/node_modules/karma/bin" 
14
votes

It is recommended to install karma with its Command-Line-Interface (karma-cli) which will take care of fetching the appropriate karma. You can also install a different local version specific to each project you're working on and karma-cli will pick the appropriate one.

From the karma installation page:

Typing ./node_modules/karma/bin/karma start sucks so you might find it useful to install karma-cli globally:

npm install -g karma-cli

Now, check that karma was installed by typing:

karma start

You can also check that karma was installed by going to this directory:

cd /usr/local/lib/node_modules/karma

Good luck!

2
votes

Don't need to completely uninstall node.js

Just

sudo rm -rf /usr/local/lib/node_modules/npm/

Then
install node.js

Then
reinstall karma

This worked for me.

2
votes

I had to add export PATH="$PATH":/usr/local/lib/node_modules/npm/node_modules/karma/bin after installing karma with sudo npm install karma.

hope this helps.

1
votes

Just go to test.sh:

Find: $BASE_DIR/../node_modules/karma/bin/karma start $BASE_DIR/../config/karma.conf.js $*

Replace with: /usr/local/bin/karma start $BASE_DIR/../config/karma.conf.js $*

Or: karma start $BASE_DIR/../config/karma.conf.js $*

1
votes

I was also facing the same issue. It looks like karma for command line is a separate package which can be installed by

npm install -g karma-cli

0
votes

When upgrading from Karma 0.10 to 0.12 the link to the karma executable is removed.

You can get it back with

cd node_modules/.bin
ln -s ../karma/bin/karma karma
-21
votes

Try re-installing node.js. There are lots of ways to install it, but I recommend downloading from nodejs.org

If that doesn't work, you may try to re-install karma.