Jonathans Blog

computer, laptop, tech, blue computer, blue laptop, blue tech, computer, laptop, tech, tech, tech, tech, tech

Setting Up the Perfect Arch Linux Development Environment in 2026

Jonathan Mitchell
· ·

Arch is the distro people either love or warn you about. For development it has one huge advantage: everything is current, all the time, and the Arch User Repository (AUR) packages almost anything you could want. This guide follows the same structure as my Mac development environment and Ubuntu development environment posts, adapted for a rolling release.

I’m assuming you already have a booted Arch system with a desktop. If not, the official installation guide on the Arch Wiki is still the best documentation in Linux, and the bundled archinstall script is a perfectly respectable shortcut.

pacman and the AUR

Update fully before installing anything. On Arch, partial upgrades (pacman -Sy followed by installing one package) are the classic way to break a system, so always use -Syu.

sudo pacman -Syu
sudo pacman -S --needed base-devel git github-cli zsh curl htop openssh

For the AUR you’ll want a helper. I use paru; yay is equally good. Both are themselves AUR packages, so you build the first one by hand:

git clone https://aur.archlinux.org/paru.git
cd paru
makepkg -si

From then on, paru with no arguments upgrades both repo and AUR packages. Read the PKGBUILD diff it shows you on first install. AUR packages are user-submitted and not vetted, so that review step is your security model.

Git and GitHub

git config --global user.name "Your Name"
git config --global user.email "you@example.com"
git config --global init.defaultBranch main

ssh-keygen -t ed25519 -C "you@example.com"
gh auth login

Shell

zsh plus a couple of plugins from the official repos gives you a fast, sane shell without a framework:

sudo pacman -S zsh-autosuggestions zsh-syntax-highlighting starship
chsh -s /usr/bin/zsh

Add eval "$(starship init zsh)" and the two plugin source lines to ~/.zshrc. Keep that file in version control from day one; the final post in this series explains how to manage your dotfiles with chezmoi.

Languages and runtimes

Arch’s own packages are so current that you can often get away with pacman -S nodejs npm python php composer. The catch is that a system upgrade can move your Node or Python major version under you mid-project. For anything with a pinned version I use mise, which is in the official extra repo:

sudo pacman -S mise
echo 'eval "$(mise activate zsh)"' >> ~/.zshrc
exec zsh

mise use --global node@24
mise use --global python@3

Projects then carry their own mise.toml, and a pacman -Syu can’t change what they run on.

Docker

Docker is in the official repos. Enable the service and add yourself to the docker group (remember that group is root-equivalent):

sudo pacman -S docker docker-compose docker-buildx
sudo systemctl enable --now docker.service
sudo usermod -aG docker $USER

Log out and back in, then check with docker run --rm hello-world. If you prefer rootless containers, podman is also in the official repos and behaves the same way as on Fedora.

Editor: pick your VS Code carefully

This trips people up. The code package in the official repos is Code – OSS, built from the open-source codebase. It uses the Open VSX marketplace and some Microsoft extensions (Remote – SSH, Dev Containers, Pylance and others) won’t work. If you need those, install Microsoft’s build from the AUR:

paru -S visual-studio-code-bin

If you live in the terminal, Neovim and Helix are both a single pacman command away and stay very current on Arch.

AI coding tools

Install Claude Code with the native installer so it updates itself independently of pacman. Don’t use sudo:

curl -fsSL https://claude.ai/install.sh | bash
claude --version
claude doctor

Keeping a rolling release healthy

  • Read the news at archlinux.org before big upgrades. Manual interventions are rare but real.
  • Install pacman-contrib and enable paccache.timer so the package cache doesn’t fill your disk.
  • Use Btrfs with snapshots (Snapper or Timeshift) so a bad upgrade is a reboot away from being undone.
  • Upgrade little and often. A weekly upgrade is far less painful than a six-month one.

Wrapping up

Arch rewards a bit of discipline with a fast, lean and absolutely current Arch Linux development environment. If you want something newer than Ubuntu but less hands-on, try the Fedora version of this guide; for Windows machines, see the WSL2 deep-dive, which can even run Arch as a WSL distribution.

,

Leave a Reply