start command gives spawn ./ngrok ENOENT: Error about ngrok-for-vscode HOT 9 CLOSED

This is weird, as I'm also getting this myself. Will look into it as soon as I can.

Yes! Super weird. I cleaned VSCode caches, downgrade the version of ngrok-for-vscode, reinstalled, and none of them did not work.

from ngrok-for-vscode.

This is weird, as I'm also getting this myself. Will look into it as soon as I can.

from ngrok-for-vscode.

Same here - nothing much to add but it seems to be around the way spawn is used. could be related to local Node.js version?

from ngrok-for-vscode.

I thought it might be something to do with the way spawn was called in the ngrok package, and initially changing ./ngrok to ngrok fixed things. But that was only because it was then calling on my globally installed ngrok executable, not the one provided by the ngrok Node package. So that was a dead end.

It appears that the ngrok executable that is downloaded is present, which makes no sense as it then can't find it (ENOENT).

I wonder if this has anything to do with npm upgrades and how processes are run postinstall.

Other than that, I'm a bit lost right now.

from ngrok-for-vscode.

It's really super weird. I really don't want to mix things up, but I have another MacBook with the same environment as I currently use (node versions, VS code versions, etc.) It doesn't have such an issue. So I'm not sure if it is related with node.

from ngrok-for-vscode.

It's really super weird. I really don't want to mix things up, but I have another MacBook with the same environment as I currently use (node versions, VS code versions, etc.) It doesn't have such an issue. So I'm not sure if it is related with node.

I recently noticed that my second Macbook started having the issue. Then, realized the vscode updated. So I guess it is a vscode related issue.

from ngrok-for-vscode.

Thanks for the update, at least we're finding a reason for consistency and I have somewhere to look. Hope to sort this soon!

from ngrok-for-vscode.

Ok, turns out this was a problem upstream in ngrok which I have fixed.

Update ngrok-for-vscode to version 1.8.4 and it should work again.

from ngrok-for-vscode.

Ok, turns out this was a problem upstream in ngrok which I have fixed.

Update ngrok-for-vscode to version 1.8.4 and it should work again.

Thank you, Phil!

from ngrok-for-vscode.