Hi, we've recently migrated our docs and added some new pages. If you would like to help translate this page, see the "Edit this page" link at the bottom of the page.
Here are some common questions regarding
WSL1 (Windows Subsystem for Linuxopen in new window 1) is not officially supported. Some aspects of
asdf may not work properly. We do not intend to add official support for WSL1.
WSL2 (Windows Subsystem for Linuxopen in new window 2) should work using the setup & dependency instructions for you chosen WSL distro.
Importantly, WSL2 is only expected to work properly when the current working directory is a Unix drive and not a bound Windows drive.
We intend to run out test suite on WSL2 when host runner support is available on GitHub Actions, currently this does not appear to be the case.
Newly installed exectable not running?
npm install -g yarn, but cannot execute
yarn. What gives?
asdf uses shimsopen in new window to manage executables. Those installed by plugins have shims automatically created, whereas installing executables via an
asdf managed tool will require you to notify
asdf of the need to create shims. In this instance, to create a shim for Yarnopen in new window. See the
asdf reshim command docs.
Shell not detecting newly installed shims?
asdf reshim is not resolving your issue, then it is most-likely due to the sourcing of
asdf.fish not being at the BOTTOM of your Shell config file (
config.fish etc). It needs to be sourced AFTER you have set your
$PATH and AFTER you have sourced your framework (oh-my-zsh etc) if any.