asdf VS volta

This, but here are some things I've learned to do:

* Use a .local directory under my home directory instead of ~/bin. That's a great prefix when installing from source or tarball at the user level, keeps the top-level of the home directory from getting cluttered with /share /lib /include /etc /lib etc. etc.

* Reach for the package manager first when installing new software, unless there is a good reason not to. It makes keeping things up-to-date easy, and since I use Arch, which uses a rolling release, you pretty much get the latest stuff.

* If I can't get what I want from the package manager, I'll look at what is available using asdf-vm (https://asdf-vm.com/), and failing that, build from source or install from tarball.

* I don't use snap or the like.

I gave up on Windows over 20 years ago, and I can't say enough how liberating it has been. One of the nicest things is that there is a distro for almost every need (see https://distrowatch.com/). I use Arch; but your use case may point to a beginner-friendly distro, such as Mint, Ubuntu, etc., or a repeatable install type of distro, such as NixOS or Guix, or many others.

# Download asdf git clone https://github.com/asdf-vm/asdf.git ~/.asdf --branch v0.15.0 # Add the following to ~/.zshrc . "$HOME/.asdf/asdf.sh" # Optional: Completions are configured by either a ZSH Framework asdf plugin # or by adding the following to your .zshrc: fpath=(${ASDF_DIR}/completions $fpath) autoload -Uz compinit && compinit

asdf is a popular version manager that uses a technique called "shimming" to switch between different versions of tools like Python, Node.js, and Ruby. It creates temporary paths to specific versions, modifying the environment to ensure that the correct version of a tool is used in different projects. However, this method can introduce performance overhead due to how these shims work.

I use asdf and direnv to manage my toolchain at the project level, so to improve the integration with Emacs I installed envrc.

Use asdf (https://asdf-vm.com/) to manage your Ruby versions.

You should be able to do

$ asdf plugin add ruby

$ asdf list all ruby (you'll see 3.4.1, the latest is available)

$ asdf install ruby 3.4.1

And now you can use Ruby 3.4.1 with no issues. Follow that up with

$ gem install bundler

$ gem install rails

$ rails new ...

The toolchain can be installed via Rustup, or (my preferred way) using asdf.

FROM ubuntu:24.04 # Atualiza o sistema e instala as dependências RUN apt-get update && apt-get install -y \ make build-essential libssl-dev zlib1g-dev \ libbz2-dev libreadline-dev libsqlite3-dev wget curl \ llvm libncurses5-dev libncursesw5-dev \ xz-utils tk-dev libffi-dev liblzma-dev \ git nano sudo # Adiciona um novo usuário RUN useradd -m -s /bin/bash usuario && \ echo "usuario:123" | chpasswd && \ usermod -aG sudo usuario # Da permissões sudo sem senha para o novo usuário RUN echo "usuario ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers # Comando inicial para rodar o container no terminal do novo usuário USER usuario # Instala e configura o asdf RUN git clone https://github.com/asdf-vm/asdf.git ~/.asdf --branch v0.14.1 RUN echo '. "$HOME/.asdf/completions/asdf.bash"' >> ~/.bashrc && \ echo '. "$HOME/.asdf/asdf.sh"' >> ~/.bashrc CMD ["/bin/bash"]

Volta: Which is a newer, fast option that works across macOS, Linux, and Windows. Volta can intelligently manage Node versions (and other tools like Yarn) based on your project's package.json, ensuring seamless switching as you move between projects. (Volta.sh)

The launch.json file described in the official Bun VS Code extension did work, especially when changing the Bun location to node_modules/.bin/bun. However, this caused serious conflicts when using Volta.sh.

In the past I've used nvm, n, volta, corepack, nodeenv. While they all have their own strength, I converged to using proto as the tool of choice.

To install Volta head over to https://volta.sh/ and get the appropriate installer package for your operating system, I'm using Ubuntu and all we need for this is:

Alternatively, you may download an installer and perform a manual installation from GitHub.

You’ll need Docker installed to follow the steps required to containerize Workerd. If you don’t already have docker installed, you can find a guide to do so here. You’ll also need Node.js installed to run the CLI tools we’ll use to compile the hello-world app later on.

Volta is a version manager that goes beyond the scope of Node.js, unlike NVM, to manage other Javascript tools like yarn, NPM, and even Rust. It is a good alternative to NVM, as it has the unique ability to automatically switch versions based on project requirements, which NVM doesn’t have.

For greater flexibility in managing multiple versions of Node.js simultaneously, consider a version management tool like Volta: