diagnostic-languageserver
nvim-lsp-ts-utils
Our great sponsors
diagnostic-languageserver | nvim-lsp-ts-utils | |
---|---|---|
16 | 30 | |
405 | 432 | |
- | - | |
1.6 | 8.0 | |
3 months ago | almost 2 years ago | |
TypeScript | Lua | |
MIT License | The Unlicense |
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.
diagnostic-languageserver
-
Vim - Using clippy as a linter
I'm not using the rust-analyzer plugin actually. I'm using the system installed rust-analyzer and diagnostic-language-server which integrates it with vim. Is there a flag or something to make rust-analyzer return clippy results as well?
-
diagnosticls-configs-nvim - pre-defined linter and formatter configs for diagnostic-languageserver
For those who use diagnostic-languageserver, this plugin provides a list of pre-defined configurations for you to use without the hassle to figure out the config on your own. Making it easier to integrate with less code.
- How to determine which linter is currently being used?
-
Eslint Lua Solution?
So reading through everyones suggestions it seems like diagnosticls is the way to go. Looks like this is the official neovim solution https://github.com/iamcco/diagnostic-languageserver formerly https://github.com/nvim-lua/diagnostic-nvim
-
Config to edit bash scripts with fancy LSP features, linting and formatting
Does anybody have such? Maybe you could share your experience? I use coc.nvim. My eyes fell on these 3 tools. The first one is language server and it has coc extensions coc-sh. But others are not so I am not sure which vim plugin should I use to hook them up: besides diagnostic-languageserver there are syntastic and neomake - bash-language-server - shellcheck - shfmt
-
Neovim LSP and typescript
>https://github.com/iamcco/diagnostic-languageserver
-
TypeScript: ESLint code actions and (experimental) diagnostics / formatting
I also added 2 experimental features designed to reduce the amount of boilerplate required to get a functional TypeScript development environment. diagnostic-languageserver and efm-langserver are powerful, but they can be tough to set up for new users, so I wanted to implement low-config, out-of-the-box alternatives for formatting and linting:
-
Losing my mind with formatting
I’ve personally never gotten efm to work at all, and I never figured out why (much like your situation). I use diagnostic-languageserver, which worked like a charm the first time. I’ve heard some users say it’s slower (TypeScript versus Go), but I’ve never had any speed issues.
-
Neovim - Why I'm switching to Native LSP over CoC
Aside from that, the biggest difference versus CoC is the ecosystem, which affects setup / tweaking time and code actions. I was able to set up ESLint diagnostics with diagnostic-languageserver, but it doesn't integrate with typescript-language-server at all, and I haven't been able to set up ESLint fixing + Prettier, either, All of that is trivial with CoC.
-
LSP and pylama…
Some LSP like diagnostic language server and efm language server do that for you. However, you will need to do some manual setup yourself for pylama to work with them, unfortunately, I don't see either of them have an example for pylama so you will have to write one yourself for those LSP servers.
nvim-lsp-ts-utils
-
New plugin to support LSP file operations
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
-
Telescope sometimes takes me to the wrong line
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.
-
Neovim setup for fullstack web development with typescript.
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.
- Is it possible make lsp definition preview more readable/pretty, and add colors or tree-sitter suport?
-
Is neovim good for webdevelopment?
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.
-
What LSP are you using for ReactJS projects and does it have auto imports?
Hi, I just found out about this https://github.com/jose-elias-alvarez/nvim-lsp-ts-utils , I might help you.
-
Typescript: Coc or Built-in LSP?
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.
-
Neo-tree now supports floating windows!
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
-
Anyone have tips to move from VS Code to Neo Vim for React development?
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.
- Sort and remove redundant imports
What are some alternatives?
null-ls.nvim - Use Neovim as a language server to inject LSP diagnostics, code actions, and more via Lua.
typescript-language-server - TypeScript & JavaScript Language Server
nvim-lspconfig - Quickstart configs for Nvim LSP
refactoring.nvim - The Refactoring library based off the Refactoring book by Martin Fowler
efm-langserver - General purpose Language Server
vim-js-file-import - Import/require files in javascript and typescript with single button!
coc-spell-checker - A basic spell checker that works well with camelCase code for (Neo)vim
neomake - Asynchronous linting and make framework for Neovim/Vim
vscode-eslint - VSCode extension to integrate eslint into VSCode
syntastic - Syntax checking hacks for vim
nvim-autopairs - autopairs for neovim written in lua