Move an asdf project to OMG

You have a project with .tool-versions and want to try OMG's package commands or task runner without losing a working asdf setup. Keep asdf installed while you test one runtime and one project task.

Current asdf is a Go binary and still uses shims to select executables. OMG reads supported .tool-versions pins and adds its installed runtime directories to PATH through a shell hook. The two tools keep separate runtime installations.

For a project with one supported Node.js version in .tool-versions, omg use node reads the pin and installs or selects that version in OMG's own data directory. OMG recognizes the common asdf nodejs name as node. It does not reuse files in asdf's installs directory.

In a separate Bash session, activate OMG's hook and inspect the command path and version inside the project. The hook selects installed runtimes when you change directories. Use the shell integration guide for Zsh or Fish.

At the next shell prompt, check where node resolves and which version runs. The hook updates the path when Bash displays a prompt.

If the version and path match the OMG installation you selected, run your project's usual tests. If you decide to keep OMG, remove the asdf shims directory from this shell's PATH setup and keep the OMG hook in the shell profile. Keep .tool-versions and the asdf installation until your projects pass their own checks.

asdf remains the better fit for a project that needs one of its plugins or shim behavior outside an interactive shell. OMG is useful when its supported runtimes can share a CLI with OS package commands and project tasks. The migration does not require changing .tool-versions, deleting asdf, or running omg migrate.

Start with the OMG installation guide if you have not installed it. The runtime reference lists supported tools, and the installation guide explains the hook before you change your profile.