Language Server support

[Sysix]

Hello 👋

I would love to support --type-aware flag for the oxc_language_server.
At the moment, I do not know if all the use cases are supported:

File Content in Memory

oxc_language_server supports linting when typing. This means, that the file content (for multiple files) on the file system is probably outdated.
Preferable, some command flag could be run to identify different files in memory.

Keep the Command running

Because we are supporting on type. The lint command is executed multiple times in a short time. To safe resources, a command which accept streaming stdin would be preferable.

Create own LSP Server?

Vue Language Server 3 splits now the logic between typescript and vue and created a bridge between them:
vuejs/language-tools#5456

The way vue language server communicate with typescript language server.
In version 2, in order to drop the takeover mode for a more compatible solution with typescript language server, another layer of complexity was introduced (named pipes server) to help vue language server communicate with typescript language server(vue tsserver plugin). However, it seems caused many issues since v2 was released. Therefore, in the new major version, it has been removed and the responsibility of communication transferred to the lsp client side.

I do not like this idea TBH. The oxc_language_server should be plug and play like the CLI tool oxlint. Setting up the editor for it is not a great experience.
Some editors support .toml/.yml configuration with servers. These editors would now need a custom script / plugin to run with type aware linting.

[camc314]

I think we can just pass it via stdin. from my limited understanding of tsgo, there is a vfs (virtual file system), so it'll go something like this

1. pass current file content + rules etc via stdin
2. tsgolint uses the file content from stdin rather than from the disk (we seed the vfs with the content from a stdin)
   3 tsgolint returns errors

i believe turning tsgolint into a proper lang server would be a much bigger, non trivial task, that we should definitely consider out of scope for the first version.

@Sysix perhaps a good first version is getting tsgolint diagnostics on save working?

[Sysix]

pass current file content + rules etc via stdin

We need to pass the file content of all unsaved files + probably the current file.
typescript-eslint rules can be fixed by another file. So keeping track of the other file content and linting the current file is key.

tsgolint uses the file content from stdin rather than from the disk

In the future, I want to support workspace/diagnostics, which will lint the project one time (like oxlint --type-aware) and will request changed after that.
Sending file content to vfs should be optional.

perhaps a good first version is getting tsgolint diagnostics on save working?

Yes, this is better than nothing 👍 Enabling the flag could disable the onType configuration.
Do you think executing the tsgolint command every time onSave is ok for now?

[Sysix]

@camc314 tsgolint any updated on in memory linting :)?
Then we can support oxc_linter::LintRunner for the server and fix the bug oxc-project/oxc#13795.
+ We could support with the solution maybe astro/vue/svelte files for the moment.

[camc314]

language server support will not be planned due to the massive complexity that it would introduce. In the mean time, we've got in-memory linting - a file's source can be provided via stdin overriding the entry on the file system

#291