expert icon indicating copy to clipboard operation
expert copied to clipboard

Official VSCode extension

Open mhanberg opened this issue 3 months ago • 11 comments

Description

We need to build and publish an official expert extension.

Workaround.

There are instructions on how to use the Lexical extension temporarily in the mean time.

https://github.com/elixir-lang/expert/blob/main/pages/installation.md

mhanberg avatar Aug 29 '25 18:08 mhanberg

Agreed. It's adding even more confusion to the fractured lsp ecosystem that the "official" one is installed using one of the previous non-official extensions

rossvz avatar Aug 29 '25 19:08 rossvz

Please add it to the Open VSX marketplace too.

https://github.com/EclipseFdn/open-vsx.org/wiki/Publishing-Extensions

kik4444 avatar Aug 30 '25 10:08 kik4444

We will. I have automation ready for all of this once we have the extension 😃

mhanberg avatar Aug 30 '25 10:08 mhanberg

I can work on this if i may 😄

urielfcampos avatar Sep 02 '25 18:09 urielfcampos

I can work on this if i may 😄

We're still not sure if we're going to duplicate one of the existing LSPs VSCode (Next LS, Lexical, or Elixir LS) or if we're going to start one from scratch or if we're going to convert the Elixir LS extension to host Expert.

I'll update the issue when the team has some direction.

mhanberg avatar Sep 02 '25 19:09 mhanberg

I can work on this if i may 😄

We're still not sure if we're going to duplicate one of the existing LSPs VSCode (Next LS, Lexical, or Elixir LS) or if we're going to start one from scratch or if we're going to convert the Elixir LS extension to host Expert.

I'll update the issue when the team has some direction.

sounds good ! I will keep an eye on it

urielfcampos avatar Sep 02 '25 21:09 urielfcampos

I do think, since this is official LS and ElixirLS is the most popular extension, it'd make most sense to transform the ElixirLS extension.

Other idea - an extension named just "Elixir" under a verified "Elixir" author to make it obvious it's now the official, complete language support for VSCode :) I don't know if you can automatically move people over to that (or if you can transform the ElixrLS extension into this).

polyjitter avatar Sep 10 '25 01:09 polyjitter

I don't think people will appreciate losing ElixirLS and its dialyzer support before the type system and Expert can replace it.

kik4444 avatar Sep 10 '25 05:09 kik4444

IMHO Elixir devs are able and willing to switch to whatever VS Code extension you're publishing. I'd just publish a new one that everyone can switch to in their own time 🙏

arnodirlam avatar Sep 12 '25 10:09 arnodirlam

@Moosieus if you have any updates on this, please post them here periodically.

mhanberg avatar Nov 12 '25 20:11 mhanberg

I agree here. I think the extension market for Elixir is already quite saturated and it's hard for any new dev picking up Elixir to know exactly what needs to be installed to gain the best DX.

My suggestion would be to take inspiration but publish a separate extension. As already mentioned above it would be very easy for any new dev to understand which one they "should pick" if we simply called it "Elixir" and gave it a verified author stamp. This extension could do it all, formatting, language intellisense, etc.

Image

krilllind avatar Nov 17 '25 09:11 krilllind