nvim-lsp-ts-utils VS typescript-language-server

Wow, cool plugin! Tsserver utils and tsserver extension support these operations https://github.com/jose-elias-alvarez/nvim-lsp-ts-utils https://github.com/jose-elias-alvarez/typescript.nvim

Interesting, I work a lot in TypeScript and with inlay hints from nvim-lsp-ts-utils enabled i do have a lot of virtual text.

I also recommend Comment.nvim along with nvim-ts-context-commentstring for easy commenting in mixed syntax files like vue SFCs. nvim-lsp-ts-utils also has some nice utility functions for typescript development.

That depends on your language server. I know the typescript language server has it. There is a plugin: https://github.com/jose-elias-alvarez/nvim-lsp-ts-utils that I think can help.

Hi, I just found out about this https://github.com/jose-elias-alvarez/nvim-lsp-ts-utils , I might help you.

I would make a feature request on https://github.com/jose-elias-alvarez/nvim-lsp-ts-utils, as this is not likely exposed via the protocol and would need to be implemented in a plugin.

There is one “recipe” for tsserver: https://github.com/jose-elias-alvarez/nvim-lsp-ts-utils/blob/main/lua/nvim-lsp-ts-utils/rename-file.lua

If you're working with React in TypeScript I'd also highly recommend nvim-lsp-ts-utils which adds some nice LSP features, for instance file renaming that automatically updates your module imports.

I'd almost given up on finding "the right" solution. Everywhere I looked, others had "solved" the issue in different ways: they were using the vtsls TypeScript LSP wrapper instead of ts_ls, or they were using coc.nvim, or the now-archived null-ls.nvim. But nowhere could I simply find a reliable configuration for a Vue language server configured natively in NeoVim.

typescript-language-server

Besides the features TypeScript itself proposed, the most important thing it brought to the community was the ability to create cool features around this compiler that enhance the developer experience and productivity. Tools like tsserver, pretty ts errors, and many others are actively improving the ecosystem for both JavaScript and TypeScript writers.

Sometimes a language server can support multiple filetypes. An example of this is tsserver, the language server for javascript and typescript. In this case a filetype plugin can still work but there is an easier way to go about it.

in this way the ts server can detect and parse the component from the microfronent, thanks to monorepos!

That was interesting, thanks for pointing it out

I was tremendously sad to see that the Typescript Language Server wasn't owned by Microsoft <https://microsoft.github.io/language-server-protocol/impleme...>, since if there was any sanity in the world a spec bump would travel with a reference implementation showing how they envision such a thing being used

But, I found that the Typescript Language Server that they did list does indeed have a semantic-tokens module in it, although it's much shorter than I would have expected from reading that section in the spec: https://github.com/typescript-language-server/typescript-lan...

I would like to use svelte language server when working on +page.server.ts files and not the typescript language server.