-
-
Notifications
You must be signed in to change notification settings - Fork 123
[Feature] Install extra tools (like lua-formatter, eslint_d, prettierd) #95
Comments
Hey! Yes this is something I'd like to do in the future too. However I am pretty sure I'd not want to put anything formatter-related in this plugin, but instead start a separate plugin for that purpose specifically. Much of the code in terms of installing, uninstalling, and the UI is very much reusable, so it should not take a lot of effort to make it happen. What's kinda holding me back atm is:
Might look into this soon, since you created an issue there might be a bigger demand than I anticipated :P |
I would recommend a companion for null-ls, it supports a ton of formatters and linters. lspconfig - nvim-lsp-installer |
I've been meaning to learn more about null-ls. Looks interesting, would definitely help by not having to ensure compatibility with all existing plugins out there. |
Could keep it one plugin and ensure that That said, many of these tools are often installed locally to a project as a dev dependency (e.g., eslint) and it should use that over the system / nvim-lsp-installer version. This is important for predictable CI, etc. |
Yes Prettier/ESLint should try and use locally installed versions first, that's how the plugins work in VS Code. |
I propose these for python developers too:
|
Cross-posting this here: pocco81/dap-buddy.nvim#71 (comment) |
Cross-posting some updates on this here: pocco81/dap-buddy.nvim#71 (comment). tl;dr: it's very much a work in progress, changes are however so significant that I really think it warrants a new plugin altogether |
Hello all. So as I've been working on this on-and-off for the past months I've ended up with something that is so fundamentally different from nvim-lsp-installer that I felt like it warranted an entirely new plugin, so that's just what I've done. I just made https://github.com/williamboman/mason.nvim public for alpha testing. Feel free to give it a spin if you'd like, for the time being only a small set of new packages have been added on top the nvim-lsp-installer base (PRs to add new packages are very much welcomed). For those who currently use nvim-lsp-installer and want to switch entirely during testing (which I recommend), the minimum you need to get started is: require("mason").setup()
require("mason-lspconfig").setup() Note that you will have to manually clean up the old installation directory that nvim-lsp-installer used - mason installs to a new one by default. |
I know they're not specifically used as LSP servers but more indirectly but servers like efm or diagnostic, but it would be cool, imho, to have the possibility to install also these external tools, like:
etc.
what do you think?
The text was updated successfully, but these errors were encountered: