-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading the "How it works" section, I'm still uncertain what's different from the regular ts lsp? #306
Comments
I am by no means an authoritative source on this matter, so grains of salts required; but my understanding is that
The translation done by Someone please correct me if my assumptions are wrong. |
coc does translation too, and that's supposedly faster than everything. Translation might not be the only factor here. It might have to do with not blocking the process. This is a separate plugin and has access to nvim apis. Specifically, the handlers are wrapped in Another possibility is the lua plugin is being pre-compiled and runs faster than node apps. 🤷♂️ Maybe the ultimate TS lsp would be: nvim -> lua plugin -> LSP translator in rust/go -> tsserver |
The ultimate TS LSP would be |
Was reading: https://github.com/pmizio/typescript-tools.nvim?tab=readme-ov-file#-how-it-works
and I'm still not clear why or how typescript-tools is better than
ts_ls
.Any additional insights would be greatly appreciated <3
I have run in to all the problems the README has described for large monorepos (slow, etc), but I don't see how typescript-tools does anything different?
The text was updated successfully, but these errors were encountered: