docs(readme): justify why mason-lspconfig.nvim is needed

[matu3ba]

Prerequisites: mason-lspconfig.nvim, mason.nvim and nvim-lspconfig (Optional for advanced users, but required for this guide).

Context: https://github.com/williamboman/mason-lspconfig.nvim/blob/dfdd771b792fbb4bad8e057d72558255695aa1a7/lua/mason-lspconfig/typescript.lua.

I don't understand what "vendored Typescript installation" means in this context. Afaiu, mason is supposed to install the ts server and also adjusting the internal neovim PATH-eqivalent, so whatever nvim-lspconfig is using to spawn the server "just works". So at least to me it feels superfluous.

In my local setup there is no need for mason-lspconfig.nvim. Can you clarify?

Also, many thanks for the new plugin in Rust. It feels much more snappy and appropriate for non-gui stuff.

[matu3ba]

I did also try to use it for completion of import { HttpClient, HttpHeaders, HttpResponse, HttpEvent} from '@angular/common/http';, but that did not work and it could not find the http module or symbols within it (HttpClient, HttpHeaders, HttpResponse, HttpEvent).

Does this mean, that the dependency is for not yet implemented functionality or is this a bug or a broken setup on my side?

[KillTheMule]

You sure you're on the right repo? You seem to be talking about typescript, while this is an LSP for typst, a typesetting system.

Question is legitimate, though, I'm using this without mason.

[matu3ba]

You sure you're on the right repo?

Lmao. Not really.