gitpod VS node-pre-gyp

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.

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.

Worst case there are services like GitPod or GitHub CodeSpaces which offer you a development ready container where you can write and execute your code. You could also just run a Python 3.11/12 container on your machine and use VSCode's Container Plugin to develop in that locally.

https://gitpod.io/ ain't bad either. It gives you per-repo docker environments that include vscode in the browser.

Some of you may know that Gitpod supported a self-hosted installation until December 2022 when it was abandoned. I was part of the self-hosted team until I was laid off in January.

Indeed, Snowboy uses node-pre-gyp which helps to publish and install Node.js C++ addons from binaries. So when a new Node.js version is shipped, node-pre-gyp must update its listing of the supported targets by specifying the:

Node is like 95% OK with ARM chips, so you might have a tricky dependency. Every time I had problems it was related to something depending on node-pre-gyp, there is an issue about it .