Florian Verdonck

@Bushuo, there still seems to be something up with the legacy commands: 

Thank you so much 😊!

This is how gleam does it. You install it and their cli has a command to start the lsp server. All logic happens there and you have thin clients that...

I have one question: Currently, the LSP tooling calls OCaml components externally. These tools read artifact files from the `lib` folder. It's somewhat fortunate that this setup works as it...

I believe `v12` is a perfect opportunity to introduce `rescript lsp`. Users on older versions can continue using the current VSCode plugin. While it's a commendable goal to support all...

This feels very similar to the other sample. I would be fine with replacing it with this one. Additionally, users aren't being directed to this sample if that is the...

It should be replaced with something I described [here](https://github.com/fable-compiler/vite-plugin-fable/issues/22#issuecomment-2742598440). Most package managers block `postinstall` scripts these days, so you may need to address this issue moving forward.

Publishing happens locally right now. Would be great to have this in CI when a tag is pushed.

The source of truth is the [changelog](https://keepachangelog.com/en/1.1.0/), where users can easily check if an item is unreleased. I believe there is a package available that can read the latest version...

Hello, thank you for your interest. At first glance, I don't think this is deemed problematic by the current userbase. (As it was never brought up until now) Could you...