You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed you have ngrok as the suggested tunnelling solution in your README and you also have a script in package.json. However, it has a few issues
Its closed source and proprietary. Because you can't review the source code, you can never be 100% sure what you are really installing
You can't self host ngrok
Its not part of the NodeJS ecosystem, you have to install it separately. There is an NPM wrapper package but it just wraps around the ngrok binary.
So, i'd like to update your docs to add tunnelmole. It has the following advantages
Its fully open source with a permissive MIT license
Optionally, Tunnelmole can be self hosted with the Tunnelmole Service. Otherwise it will use the default service at tunnelmole.com.
Its on NPM. You can run npx tmole 3000 without installing anything and it will work.
Here's the difference in terms of set up and usage
I've noticed you have ngrok as the suggested tunnelling solution in your README and you also have a script in
package.json
. However, it has a few issuesSo, i'd like to update your docs to add tunnelmole. It has the following advantages
npx tmole 3000
without installing anything and it will work.Here's the difference in terms of set up and usage
Ngrok
First download and install from ngrok.com
Tunnelmole
Various installation options including
npm
, copy and paste shell one liner, building from source etc available in the READMEFor example, you can install with
curl -O https://install.tunnelmole.com/2334d/install && sudo bash install
then runThere are a few options here
I'm also interested in improving upon your current
ngrok
script inpackage.json
.I could add something like
This will work as is. Unlike ngrok it won't require installing anything.
Let me know your preference and if you'd like me to make a PR with the changes.
The text was updated successfully, but these errors were encountered: