[IntelliJ 2025.2] Initial Git Commit w/ out-of-the-box Phoenix Project causes Elixir Plugin to Partially Lose Functionality #3708
Description
Describe the bug
I committed a freshly created Phoenix project (Phoenix v1.8) to my local machine, then my Elixir plugin started losing syntax highlighting, intellisense (technically, this still worked, but I had to manually force the suggestions box to pop up with Ctrl + Space). I began seeing a slew of org.elixir_lang.beam.StubBuilder - No stub built for file errors for various .beam parser files, in addition to a couple of SEVERE - #org.elixir_lang.mix.Dep errors.
To Reproduce
Steps to reproduce the behavior:
- Go to any folder
- Execute
mix phx.new (whatever you wanna name it)- mine wasmix phx.new phoenix_sandbox - Open the project with IntelliJ
- See a large volume of uncommitted files
- Commit all to your local Git repo
- Lose syntax highlighting, intellisense, etc, and see plugin errors in IntelliJ logs
Expected behavior
I expected the project to be cleanly committed to disk without affecting the plugin functionality.
Screenshots
Logs
Desktop:
- OS: macOS
- Version: Sequoia 15.6
Erlang:
- Installer: asdf
- Version: 28.0.2
Elixir:
- Installer: asdf
- Version: 1.18.4-otp-28
Plugin:
- Version 21.0.0
Additional context
I have the exact same plugin and Erlang + Elixir install and setup on my work machine and it works perfectly fine, but then again, on that machine I'm only committing small volumes of files, nothing so big that it'd cause the plugin to freak out.