freewebwithme
Using vs code and installed ElixirLS: support and debugger.
And I got an error popped up on start up says
Failed to run ‘elixir’ command. ElixirLS will probably fail to launch. Logged PATH to Development Console.
I think elixir command is in current path
which elixir
/home/user/.asdf/shims/elixir
and
echo $PATH
...........:/home/user/.asdf/shims:.....................
What is my problem?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
At WyeWorks, we believe great software is built by combining technical excellence with genuine human connection
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #blog-post
- #ai
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 11 to 20- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
lukaszsamson
Does your integrated terminal in vscode have the necessary envs? I guess thats what vscode uses to launch elixir-ls
NobbZ
Try a local user install as described by asdf rather than some package manager that installs system wide.
Facundo
Thanks @NobbZ
Installed
asdfagain from sources –not using brew- and it works smoothly.@lukaszsamson my integrated terminal is
zshand loads every other terminal outside of VSCode.Nefcairon
Hello,
I am using VS Code via Windows 10/WSL (erlang/elixir installed via asdf) and I also get
I even do not know where/what this “Development Console” is (google didn’t help).
Is someone able to help me?
Facundo
Click on View → Terminal
Select
outputtabThen select ElixirLS from the dropdown
wdiechmann
@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.0I may have installed asdf with brew first - but my current installation is tucked away safely in $HOME/.asdf
Tried
iexfrom CLI only to learn that elixir wasn’t the issue at all -erlwas! (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.1out of the way - all was good in VSCode on macOS BigSur landthepeoplesbourgeois
Actually, “development console” in that error refers to
Chromium’sElectron’sVSCode’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.wallyfoo
This ended up being the solution for me here on Groundhog’s Day, 2022. I forgot to set my global erlang asdf.
Rectified, relaunched, resplendent.
jmnda
Setting
erlangandelixirglobally solve the issue for me as wellasdf global erlang <your_version>asdf global elixir <your_version>JVMartyns
I solved it using:
sudo dnf install erlang-dialyzer
sudo dnf install erlang-edoc
asdf local elixir 1.13.3
asdf local erlang 24.3.4