-
Notifications
You must be signed in to change notification settings - Fork 4.3k
npm installation fails #429
Comments
@bserem Same here, I used this installation method on my last machine a few months ago, but after reinstalling it yesterday it doesn't work anymore. I get the same error message. |
Same issue here on Mac OS Sierra, npm 5.3.0 |
Managed to install it by using yarn instead of npm |
I was having the same issue with npm install -g exp. |
for node installs on linux mint and ubuntu where it gets installed in /usr/bin/node and /usr/lib/node_modules, this did the trick for me: $sudo yarn global add ngork --modules-folder /usr/lib/node_modules |
^^ Small typo on ngork (we want ngrok). It worked for me too! (Ubuntu) |
Same problem here. Using Arch linux. |
This is didn't work for me on a generic EC2 Linux AMI but I have it working on another EC2 Linux AMI where it works perfectly. Both instances are setup the same way but for some reason this one will not let me setup ngrok. I get the same exact error that started this thread. I've tired as root several times and rebooted, no idea whats up. Same versions between each instance. |
The same for my on Windows 10, I test with npm and yarn, download fine the package and never end of unpack . Any Idea of what happen?? |
Same issue here... I was hoping this has been fixed already. |
Yeah I'm experiencing this on a brand new Ubuntu build within an ESXI environment. |
Same here, brand new Ubuntu build Xenial under virtualbox |
Yeah, so I downloaded ngrok directly from the source on my Ubuntu machine using wget and unzipped and placed within the usr/local/ folder and it works like a charm now. Forrest whatever reason downloading via package manager ngrok fails. |
I removed sudo from the beginning of the command and it installed with npm (was failing with sudo)! BTW, I was installing "sudo npm install exp --global" when I saw the above error mentioned above. |
|
@ankibalyan doesn't work on MacOS High Sierra |
This one did the trick for me:
|
brezzhnev...that also worked for me. |
@brezzhnev This is the answer. But why is this now necessary and can it be fixed? |
@brownbl1 just grabbed from here: appium/appium#10293 (comment) Actually, have no idea, would like to ask this question to devs as well :) For me, npm is like a black box, you never know what could happen whenever you try to install or update dependencies. |
livesafer! |
I just saw one line with |
Same problem on Windows 10. Will this be fixed?
It only works with unsafe-perm param. |
It worked for me... great, thanks |
Chiming in here in 2020 - still the same issue of not being able to find module I'm on a Ubuntu 16.04.6 LTS machine, Node 12.17.0 via NVM Surely passing EDIT: Just found bubenshchykov/ngrok#115 (comment) It looks like until postinstall.js is removed, Linux and macOS users have to do it this way. |
if you're on a macbook with an M1 processor and faced this problem again, make sure that u're using at least the 4.2.2 package version of ngrock good luck |
|
After Using npm i -g ngrok --unsafe-perm=true --allow-root (windows) also I get below error |
Virtualbox Ubuntu 18.04
ngrok - downloading binary https://bin.equinox.io/c/4VmDzA7iaHb/ngrok-stable-linux-amd64.zip |
having the same exact issue, but on Mac OS, anyone has a clue? |
having the same issue on Mac OS |
upgrading to node |
Thank you for opening this issue! As of April 2016, the ngrok service has permanently moved to https://ngrok.com/. To join the community and file bug reports or feature enhancements for the ngrok agent, please go to https://github.com/ngrok/ngrok. This repository is no longer actively maintained and will be archived soon to reduce confusion with the latest ngrok versions. We thank you for the continued support of ngrok and look forward to seeing you over at ngrok.com and the ngrok Community Repo. |
As of today I can't install ngrok via npm, I get the following output on Debian with node 5.0.4:
Installation was working fine 10 days ago.
This also breaks the installation of https://github.com/expo/exp
The text was updated successfully, but these errors were encountered: