-
Notifications
You must be signed in to change notification settings - Fork 316
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
Doesn't work with Node.js v17.0.1 #254
Comments
We are also seeing this issue! It affects the entire command, even On MacOS (tried both M1 and Intel systems):
While on Linux (Ubuntu in this case), it still works:
|
I have narrowed this issue to
The ngrok in |
Ah, interesting. Thanks for investigating @nsainaney and for raising the issue with Will wait to see what the |
@philnash - just submitted a PR for this. Would appreciate it if it could get reviewed, merged, and published. Thank you |
Between the PR and nodejs/node#40702, I have tested the package on Node 17 and everything seems to work now |
Hey @nsainaney, sorry I haven't got to the PR yet. What is the relevance of nodejs/node#40702 to this though? I'm not sure I see a connection. |
@philnash, we were using an axios based client that was initialized with |
Ha, ok. I'll get to the PR review later. Thanks! |
I just ran into this issue as well. Have you had a chance to look into the PR? |
just try to download(https://ngrok.com/download) the M1 zip file and drop the ngrok.exec file into "/opt/homebrew/bin/", finally it works! |
I have some issue on win10 and macos. I solved it with replacing bin files in node_modules with files from ngrok.com |
I'm having the same issue. My
Looking that file here in the repo, looks like it's actually with the wrong version of it. I don't think that should be the content of the file. |
The fix for this has been released as part of version 4.3.0 on npm now. |
Thank you so much :) |
Is there anyone with a similar phenomenon?
Here is a memo for myself.
The text was updated successfully, but these errors were encountered: