GitHub Issues
StackOverflow TagWhat is this?
asdf is a CLI tool that manages multiple language runtime versions on a per-project basis — like gvm, nvm, rbenv and pyenv all in one. You add a plugin for each language you use.
asdf is a CLI tool that manages multiple language runtime versions on a per-project basis — like gvm, nvm, rbenv and pyenv all in one. You add a plugin for each language you use.Is it yet another single-language version manager, or does it replace tools like nvm and rbenv?It replaces them: a single CLI with consistent commands for all your languages, one global config for defaults, and one .tool-versions file per project.
It replaces them: a single CLI with consistent commands for all your languages, one global config for defaults, and one .tool-versions file per project.How do I get it running?Install asdf, then simply install a plugin for each language you use and pin versions in your project's .tool-versions file. The Getting Started guide at asdf-vm.com covers the whole flow.
Install asdf, then simply install a plugin for each language you use and pin versions in your project's .tool-versions file. The Getting Started guide at asdf-vm.com covers the whole flow.Which languages can it manage?Nothing is built in — every runtime comes from a plugin you install. Ruby, Node.js, Elixir and Erlang are called out in the project description, and the docs site keeps an index of all plugins.
Nothing is built in — every runtime comes from a plugin you install. Ruby, Node.js, Elixir and Erlang are called out in the project description, and the docs site keeps an index of all plugins.What if there is no plugin for my language yet?Coverage depends on the plugin ecosystem: if your language is missing, you write your own plugin using the project's asdf-plugin-template.
Coverage depends on the plugin ecosystem: if your language is missing, you write your own plugin using the project's asdf-plugin-template.Does it switch versions automatically between projects?Yes — asdf switches runtime versions automatically as you traverse directories, driven by each project's single .tool-versions config file.
Yes — asdf switches runtime versions automatically as you traverse directories, driven by each project's single .tool-versions config file.I already use nvm and rbenv — can I migrate my configs?Yes. asdf supports existing config files — .node-version, .nvmrc and .ruby-version — for easy migration, so you don't have to rewrite every project's config right away.
Yes. asdf supports existing config files — .node-version, .nvmrc and .ruby-version — for easy migration, so you don't have to rewrite every project's config right away.Which shells get command completion?Shell completion is available for common shells: Bash, Zsh, Fish and Elvish.
Shell completion is available for common shells: Bash, Zsh, Fish and Elvish.Why did the author build yet another version manager?Per the README's 'Ballad of asdf': the author got tired of installing a version manager for every new language and learning a different command set for each, so they wrote one extendable, plugin-based manager instead.
Per the README's 'Ballad of asdf': the author got tired of installing a version manager for every new language and learning a different command set for each, so they wrote one extendable, plugin-based manager instead.What are similar projects?zoxide, oh-my-posh, inshellisense, gvm, nvm, pyenv, atuin, direnv
zoxide, oh-my-posh, inshellisense, gvm, nvm, pyenv, atuin, direnvWhich topics is it in?erlang, nushell, version-manager, elixir, fish, zsh, powershell, bash, ruby, package-manager, node, golang
erlang, nushell, version-manager, elixir, fish, zsh, powershell, bash, ruby, package-manager, node, golang