typescript-language-server
nvim-lspinstall
Our great sponsors
typescript-language-server | nvim-lspinstall | |
---|---|---|
53 | 31 | |
1,699 | 537 | |
3.5% | - | |
8.7 | 8.7 | |
about 14 hours ago | over 2 years ago | |
TypeScript | Lua | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
typescript-language-server
- Helix - Front-End Power
-
What is JSDoc and why you may not need typescript for your next project?
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.
-
A guide on Neovim's LSP client
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.
-
Suspense your federated component with caution
in this way the ts server can detect and parse the component from the microfronent, thanks to monorepos!
-
Let's write an Emacs treesitter major mode
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...
-
How do I select which LSP is currently running?
I would like to use svelte language server when working on +page.server.ts files and not the typescript language server.
-
Formatting on save not working
[[language]] name = "python" roots = ["pyproject.toml"] formatter = { command = "black", args = ["--quiet", "-"] } language-server = { command = "pyright-langserver", args = ["--stdio"] } config = {} auto-format = true [[language]] name = "rust" auto-format = true # [[language]] # name = "typescript" # auto-format = true # formatter = { command = "prettier", args = ["--parser", "typescript"]} # # pass format options according to https://github.com/typescript-language-server/typescript-language-server#workspacedidchangeconfiguration omitting the "[language].format." prefix. # config = { format = { "semicolons" = "insert", "insertSpaceBeforeFunctionParenthesis" = true } } [[language]] name = "tsx" formatter = { command = 'prettier', args = ["--parser", "typescript"] } auto-format = true [[language]] name = "javascript" auto-format = true formatter = { command = 'npx', args = ["prettier", "--config", ".prettierrc", "--parser", "javascript"] } # formatter = { command = "prettier", args = ["--parser", "javascript"]} [[language]] name = "css" formatter = { command = 'prettier', args = ["--parser", "css"] } [[language]] name = "markdown" # https://github.com/executablebooks/mdformat formatter = { command = "mdformat", args = ["-"] } [[language]] name = "json" formatter = { command = "prettier", args = ["--parser", "json"] } [[language]] name = "toml" auto-format = true # https://github.com/bd82/toml-tools/tree/master/packages/prettier-plugin-toml formatter = { command = "prettier", args = ["--parser", "toml"] } [[language]] name = "yaml" indent = { tab-width = 2, unit = " " } formatter = { command = "prettier", args = ["--parser", "yaml"] } [[language]] name = "astro" scope = "source.astro" injection-regex = "astro" file-types = ["astro"] roots = ["package.json", "astro.config.mjs"] language-server = { command = "astro-ls", args = ["--stdio"] } config = { "typescript" = { serverPath = "/Users/matteostara/.nvm/versions/node/v18.16.0/bin/typescript-language-server" }, "environment" = "node" }
-
Struggling with javascript completion with LSP
Depending on the language server version, you may be running into https://github.com/typescript-language-server/typescript-language-server/issues/631. I temporarily fixed it for me by simply sticking with an old enough server build, though judging by the latest typescript-language-server commits a very recent build from master should also work
-
There's another typescript LSP that wraps the official VSCode typescript extension and has almost the same features - vtsls
Before, I was using typescript-language-server as it is LSP compliant but it was slow and lacks the features of what VSCode's implementation has, like extracting functions, constants, types into interfaces or alias and single imports. Auto-completion was also not very predictive as sometimes it works and sometimes it doesn't. For instance, I was having trouble getting it to auto-complete common attributes like className or href in JSX projects. It could be that I may be doing something wrong but didn't find any solution on how to get it properly working.
-
What could cause my LSP to be so slow and sluggish? Takes anywhere from 1 to 8 seconds to show auto-completion results and hide/ unhide errors.
Then this is highly likely issue of typescript-language-server. You might consider opening an issue for it.
nvim-lspinstall
-
LSP question: manage an already installed server (instead of using lspinstall)
A word of caution, I believe lspinstall has been deprecated in favor of nvim-lspinstall which itself has also been deprecated in favor of mason-lspconfig
-
The SMOOTHEST yaml editing experience possible yaml-language-server neovim
kabouzeid/nvim-lspinstall will aide in installing lsp's if you want. I have chosen not to because I want to have my full setup scripted so when I setup any new machine I just run my ansible-playbook. This library is nice to just set things up quick and play with them.
- Cant get angular language server work
- Nvim-lspinstall has been archived
-
Do you use a completion plugin or use your own solution?
nvim-lspinstall
-
cmd not defined for "sumneko_lua". You must manually set cmd in the setup{} call according to CONFIG.md
I'm trying to edit a lua file, and got this error which I realize is because I didn't have the Lua language server installed. So using the LspInstall plugin, I did :LspInstall lua which was successful.
-
Enable Lsp on specific file types
Once you have it installed, you can configure it following the configuration of this file: https://github.com/kabouzeid/nvim-lspinstall/wiki. The part that ia bellow the comment "-- lsp-install" works and it was what I used initially when I didn't really know much about configuring neovim.
-
How to not have diagnostic error in a json file with comments?
I am using lspinstall to install language server. It uses this json-language-server. As the docs says jsonc is supported and it allows comments in jsonc filetypes but the lsp is not showing diagnostic if I make any other syntax error. On line 34 i have removed a comma and still lsp showing no diagnostic error in jsonc file.
- Not an editor command: LspInstall tsserver
-
[LSP]Tailwindcss not working
You could try to use the instructions that nvim-lspinstall uses to install the tailwindcss language server: https://github.com/kabouzeid/nvim-lspinstall/blob/main/lua/lspinstall/servers/tailwindcss.lua (lines 4 - 12)
What are some alternatives?
deno - A modern runtime for JavaScript and TypeScript.
nvim-lsp-installer - Further development has moved to https://github.com/williamboman/mason.nvim!
nvim-lspconfig - Quickstart configs for Nvim LSP
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
tailwindcss-intellisense - Intelligent Tailwind CSS tooling for Visual Studio Code
nvim-lsp-ts-utils - Utilities to improve the TypeScript development experience for Neovim's built-in LSP client.
nvim-compe - Auto completion Lua plugin for nvim
TypeScript - IO wrapper around TypeScript language services, allowing for easy consumption by editor plugins
vim-plug - :hibiscus: Minimalist Vim Plugin Manager
neovim - Vim-fork focused on extensibility and usability
nvim-lint - An asynchronous linter plugin for Neovim complementary to the built-in Language Server Protocol support.