gitpod VS module-alias

Gitpod: It provides a Chrome extension that opens a VS Code-based IDE right in your browser. It is best for running the project in your browser without setting up and running locally.

GitPod — Instant, ready-to-code dev environments for GitHub projects. The free tier includes 50 hours/month.

Benefit from an integrated terminal, collaboration features, diffs, and more. Gitpod

Gitpod

Tool Spotlight: Featuring insights on how Artillery and Gitpod can enhance and streamline the benchmarking process.

This is very interesting but if I read correctly OP’s question they probably mean something like Gitpod/GitHub Codespaces where the IDE is running “somewhere else” and is accessible via browser.

Before we begin the siege of the RPC we need to ensure our system is configured for building Soroban smart contracts. You have two clear options. The first is to use a virtual environment like Gitpod or Codespaces which can have everything pre-installed and configured for you. In fact here's a good hello-world Gitpod VM we've built for you.

GitPod can integrate with a range of Git repo hosts and supports a number of popular IDEs, not just VS Code. The Starter account gives you 50 hrs free per month.

But here is the thing, I want to continue to use the module-alias npm package as I find it brings better readability of the imports. I found that it requires to build a custom module loader to resolve it. I concluded that it was too much steps to achieve for a small output, then I chose to postpone the Babel dropping task. If you are interested into that specific case, there is an ongoing GitHub issue.

module-alias