2025.2 Roadmap

[joshuataylor]

Finally feeling well again after many months, and I'm dedicating Saturday afternoon/Sunday to finalising a whole bunch of work.

Step 1: Finish outstanding PRs

This release requires a bit of work, but we're fairly close, and we have some exciting features.

1. We need to upgrade to Kotlin 2.x, which is required for 2025.1+. I did this a while ago, PR Kotlin 2.x support #3702.
2. HEEx injection - this is honestly one of my favourite features when working with other languages, as the SQL injection etc is super handy, and this is a great idea. Many thanks to @polymorfiq for getting the ball rolling for this, and figuring out the arcane magic incantations to do so.
3. Language Support for HEEx - This might need a bit of work in future, as these are really tricky to get right (PSI nightmares). Add language support for HEEx #3696

Step 2: RELEASE

This will support 2025.1 and below, but 2025.2 will have a few issues.

Step 3: Fix deprecated IntelliJ Plugin Platform code

Now, we'll need to fix a fair few Kotlin coroutines/threading related issues, such as #3699 .

Fun. Unknown scope.

Step 3a: Work on 2025.2 support

Every fix will be in either a canary or point release, to help fix 2025.2 support, and hopefully get the IDEs working again.

During this, we will obviously get reports in about how 2025.x+ doesn't support the way the plugin does background work not via coroutines.

Step 4: OTP/Elixir Version Upgrades

After this is merged, I will open another issue where we can track upgrading to the newer versions of Erlang & Elixir, which will make local development a bit easier (for example, installing OTP 24.3.4.6 requires openssl1, which is a pain on both MacOS/Linux).

This will require some updates to the Lexer, as there are new language features in Elixir & OTP.

A interesting experiment could be burrito, which allows you to build binaries for platforms, which would be perfect for the intellij_elixir Elixir Helpers, see https://github.com/joshuataylor/intellij_elixir/blob/main/.github/workflows/burrito-build-cross.yaml , as we can build standalone binaries that run the Erlang/Elixir app without needing that specific version, allowing easier collaboration, and support for JetBrains (trying to get them to read your issue, yet along run Erlang/Elixir is not going to happen).

Future work / fun stuff

During all this, there are obviously still lots of long hanging fruit, and hopefully we can merge these quickly.

e.g:

1. Get Canary Releases working, for testing - no more ZIPs!

[Lutrome]

I'm sorry to poke, but when will this be released? HEEx + ~H support would be a godsend for me.

I'm currently on the below IntelliJ 2025.2 build, with almost no issues from the latest stable version of the Elixir plugin (21.0.0)
IntelliJ IDEA 2025.2 (Ultimate Edition)
Build #IU-252.23892.409

[joshuataylor]

I've been trying for the last 2 days to get 2025.2 to work - there is a lot of deprecated/removed functionality.

Current issue is that ~S is now breaking, as the PSI checker now throws an error, which is the last blocker. Tracking issue - #3705

[Lutrome]

Thanks for the update, and I'm sorry if my initial comment sounded rushed - I read way too fast and thought this issue was opened 4 weeks ago for some reason, but it says "4 days ago".

I wish I could help, but I'm unfamiliar with IntelliJ's PSI.

[joshuataylor]

You're all good, no worries - also so keen for HEEX, now that's what everyone uses. i don't think anyone really does, it's such a blackbox, and you should never want to touch it :P.

…

On Sun, 10 Aug 2025 at 13:46, Nathan Olson ***@***.***> wrote: *Lutrome* left a comment (KronicDeth/intellij-elixir#3704) <#3704 (comment)> Thanks for the update, and I'm sorry if my initial comment sounded rushed - I read *way* too fast and thought this issue was opened 4 weeks ago for some reason, but it says "4 days ago". I wish I could help, but I'm unfamiliar with IntelliJ's PSI. — Reply to this email directly, view it on GitHub <#3704 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABW626DLRJLQNO3DTJ3RJD3M3MDDAVCNFSM6AAAAACDGVCTWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZSGM4DQOBQHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[irakliasatiani]

If you somehow manage to run latest elixir/erlang on any of the IDE right now, because it seems completely broken, it will be a big win already, and it's shame you're not sponsored by jetbrains itself, because it's quite important extension I think and will get more in the future.

[joshuataylor]

Here is the current roadmap for supporting 2025.2+:

1. 2025.1 and 2025.2 requires a bit of work to get working again, due to deprecated functionality.
2. If you want the plugin to "work", use 2024.x
3. To not break compatibility with 2024.x, we'll work on a new branch until it's stable enough. A new feature branch has been created (feature/support-2025-2)
4. An EAP release will be created that will allow auto updating via the Plugin Manager in intelliJ.
   1. Until then, we'll provide zips.
5. To accommodate various "experimental functionality", registry keys will be made available, this is to work around settings bugs in IntelliJ.
6. For everything else, this will be in settings.
7. Support for IntelliJ will.come first, as the SDK is slightly less hacky than RubyMine etc.
8. RubyMine and GoLand and similar IDEs are still priority, we'll sort one problem at a time

I believe this is the easiest approach, and let's users get going again.

Please report any bugs/weirdness, Ns please submit error reports - these REALLY help!

I'll update this post once the EAP releases have been uploaded.

[joshuataylor]

Newest EAP ZIP here: #3711