-
Notifications
You must be signed in to change notification settings - Fork 534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is a problem when npm install #35
Comments
Make sure you have the C++ compiler installed on your system. sudo apt install build-essential |
@sammaina In your case it's looking for the python executable (Line 2 of the error stack). Please add it to your Linux-based OSes wont have issues concerning |
@IOAyman I have gcc installed. The same error is still here. I screen shot the whole message for your reference. What possibly can it be? Thanks in advance. |
@sammaina You can follow the A.3 step of the following link to install python or add python to your PATH. Windows do not have python pre-installed. If you want to install python, please install python 2.7., since npm do not support 3. |
Similar happens with macOS, It searches for XCode or CLT but fails and crashes. |
I'm having the same issue in Ubuntu 16.04. I verified that I have C++ compiler and Python 2.7.1 installed and in path. Had Node 4, tried updating to 6.9.1, still didn't work. NPM 3.10.9. This is my stack running npm install (directory = [...]):
|
@IOAyman @yangzgnay Thanks it helped. Landed into the same error. |
Guys, it seems it's a bug with the robotjs dependency. I updated line 23 of package.json to and now |
@jotaporras |
@yangzgnay Maybe take a look at octalmage/robotjs#17 ? |
Idk but i guess it only works on mac OS. |
@jotaporras Works for me. Thanks |
I'm new to npm and Nodejs. The following error occur when I do npm install:
/bin/sh: 1: node: not found
gyp: Call to 'node -e "require('nan')"' returned exit status 127 while in binding.gyp. while trying to load binding.gyp
What should I do to continue it?
some info:
ubuntu 16.04
node v4.2.6
npm v3.5.2
The text was updated successfully, but these errors were encountered: