It might have a different view to your PATH than your shell, especially if you start it from a graphical environment rather from the terminal.
Please check the PATH logged into the console as explained by the error.
Please also check if the error persists when starting VScode from within a terminal that already is in the projects folder if you do not already open it that way. Depending on your operating system/flavor of it, you might need to run one of vscode . or code ..
Your GUI does not care about settings in .zshenv and .zprofile, both of them are used by zsh only.
Though if your installed version of Elixir-LS is recent enough (I think it became added in 0.3.0 or 0.4.0), then asdf should be found by it if $HOME/.asdf/asdf.sh exists.
@Facundo I can confirm that! Just <upgraded> my MacBook Air M1 to BigSur - and the next thing I noticed was that ElixirLS fails to start in VSCode
my .zshrc is good as is my asdf local elixir 1.12.0
I may have installed asdf with brew first - but my current installation is tucked away safely in $HOME/.asdf
Tried iex from CLI only to learn that elixir wasn’t the issue at all - erl was! (Note: I run all my workbench stuff in containers which is probably why I haven’t noticed)
Once I got my asdf global erlang 24.1 out of the way - all was good in VSCode on macOS BigSur land
Actually, “development console” in that error refers to Chromium’sElectron’s VSCode’s development tools console, which is under the Help menu header on MacOS, and… might be in a similar enough part of the Windows menu if you dig around for it a bit, @Nefcairon.