-
Notifications
You must be signed in to change notification settings - Fork 477
Expo CLI cant be installed in Linux #591
Comments
I'm using Ubuntu 18.04.2 LTS and I have the same errors! |
I solved this by installing it with yarn So npm + expo is broken somehow |
I had not yarn, but in my first attempt the terminal returns: Command 'yarn' not found, but can be installed with: apt install cmdtest I made it, but after this install, the error appears: 00h00m00s 0/0: : ERROR: [Errno 2] No such file or directory: 'global' |
Try to run without |
I made it too, but doesn't works too :( |
Having the same issues when trying to build the base image for Expo GitHub Action. |
This is related to NPM failing for both iltorb and sharp dependencies. Let's work around this by using Yarn for now. expo/expo-cli#591
This is related to NPM failing for both iltorb and sharp dependencies. Let's work around this by using Yarn for now. expo/expo-cli#591
Hello, I used npm, logs are below. logs for npm npm ERR! A complete log of this run can be found in: |
yarn worked form me too, thanks for the support :) |
yarn didn't work for me and I can't rollback to the previous expo-cli version that worked before... installing it on windows (with yarn or npm) doesn't work either. |
I have the same issue in CI using the
|
For those using npx expo-cli ... If there's no alternative and you absolutely have to install a package with native dependencies globally as root via sudo npm install -g --unsafe-perm expo-cli |
sudo npm install --unsafe-perm expo-cli |
sudo npm install -g --unsafe-perm expo-cli |
sudo npm install -g --unsafe-perm explo-cli |
Yarn alternative solved if for me as well, (mac os).. it broke down after an upgrade |
Worked after: |
After spending almost 1 day, i resolved this issue, this error is due to sharp If you are having issues during installation consider removing the directory C:\Users[user]\AppData\Roaming\npm-cache_libvips. npm install -g sharp (The installation require python 2.7 on windows and path env configuration) npm install -g expo-cli |
Ubuntu 18.04 user here. |
Try running npm install expo-cli --global instead, you need the dashes to signify it’s a flag |
Same issue here, Running |
sudo npm install -g --unsafe-perm expo-cli |
To resolve permissions issues, I followed instructions to re-install npm via Node Version Manager. I didn't have to uninstall npm before re-installing it. I followed instructions here (https://github.com/nvm-sh/nvm), which means I just ran the following command: Once the nvm installation was complete, I closed my terminal and re-opened it (to apply bash updates), and then I installed the latest stable version of npm using the "node" keyword: And, there you go, Bob's father's your father's father (Bob's your uncle). Now you can retry the npm installation and it should work. For me, I was hitting permissions errors while trying to install expo-cli via npm. When I re-ran that command after installing npm via nvm, the command worked fine. |
I tried all the above methods and none of them worked for me. |
yes it have issue in install expo |
sudo npm install -g --unsafe-perm expo-cli |
|
@edoantonioco just do |
i am getting errors with both npm and yarn. |
I am also getting same error... is it something to do windows? I am running in windows 7... :( it was working fine few days back |
sorry what is the error that you are seeing? you could not possibly be seeing the same error as the original post because expo-cli does not include sharp anymore. the other warnings are unavoidable and the result of |
i'm closing this because the original topic of this issue was installation issues due to sharp, which no longer is included in expo-cli. if you are having problems installing expo-cli please create a new issue and include information specific to what is going wrong in your situation. thanks! |
Description
In linux to install expo cli you use "sudo npm install -g expo-cli" (sudo is a requirement sadly)
I try to install expo cli, and installation fails
Also to note I reinstalled Linux Manjaro to see if the error got fixed (it doesnt)
Also, this only happens since latest expo cli, previously it worked fine.
Expected Behavior
I expected to install expo cli
Observed Behavior
The text was updated successfully, but these errors were encountered: