DEV Community

Ameya Pai
Ameya Pai

Posted on

VSCode's Local Port Forwarding in 1.82.0

Many a times, our clients or our colleagues would like to test some feature which is still running in our local hands-on. In this scenario, I used a handy tool from ngrok called secure tunnels. This would help us in local port forwarding i.e. let's say your application is running at localhost:8081. Now through the local port forwarding tool, anyone can access your application using a url generated by ngrok. I have been using this for years.
Today, I saw a new feature ( at least I assume it is new ), in VSCode i.e. 'Local Port Forwarding'. It does the same thing which ngrok. Looks like VSCode may have unintentionally put a small dent in ngrok's business. However, I found some concerns with the service.

  1. It took around 3-4 minutes at least for initial service to start. Why? ( Ngrok takes hardly 3-4 seconds )
  2. Why did VSCode want to access my Github account? It actually registered into my Github account. ( Ngrok only needs me create an account with them and create an access token which needs to be submitted during first-time setup of app in the system )

Anyways, this needs investigation. If I have time, I will do it. However, I suggest that you guys use both the services to see their pros and cons.

If you find any concern, feel free to comment. Thank you.

Image of Docusign

Bring your solution into Docusign. Reach over 1.6M customers.

Docusign is now extensible. Overcome challenges with disconnected products and inaccessible data by bringing your solutions into Docusign and publishing to 1.6M customers in the App Center.

Learn more

Top comments (0)

Postmark Image

Speedy emails, satisfied customers

Are delayed transactional emails costing you user satisfaction? Postmark delivers your emails almost instantly, keeping your customers happy and connected.

Sign up