[no description] http://git.sudomsg.com/mirror/mason/atom/lua/nvim-lsp-installer/servers/eslint/init.lua?h=main 2022-07-06T22:39:59Z 2022-07-06T22:39:59Z William Boman william@redwill.se 2022-07-06T17:41:43Z urn:sha1:5f634e0c37e723fc0c33e06b4fd5c2180178db40 2022-01-02T16:54:56Z William Boman william@redwill.se 2022-01-02T16:54:56Z urn:sha1:095ab4eb6a02d5fd3ea4b782a0e868e2c65e4427 1. This is a breaking change for the following servers, which will have to be reinstalled: - ltex - clangd 2. This is a breaking change for users who reach into the default options (for example via server:get_default_options()) to access the `cmd` property. nvim-lsp-installer no longer provides the `cmd` (except in a few instances), but instead provides an amended PATH which allows neovim's LSP client to locate the locally installed executable. To access the `cmd`, simply access it via lspconfig instead, for example like so: local default_config = require("lspconfig.server_configurations.rust_analyzer").default_config print("I can now access the cmd governed by lspconfig:", default_config.cmd) 3. This is a breaking change for 3rd party use cases that makes use of the `executable()` APIs (e.g., `npm.executable(root_dir, "tsserver")`). The recommended usage is to instead to use the canonical name of the command ("tsserver"), while providing an amended PATH, for example: local npm = require("nvim-lsp-installer.installers.npm") local server = server.Server:new { ..., root_dir = root_dir, installer = npm.packages { "tsserver" }, default_options = { cmd = { "tsserver" }, cmd_env = npm.env(root_dir), } } 2021-12-06T22:25:31Z William Boman william@redwill.se 2021-12-06T22:25:31Z urn:sha1:ca77206c1846fd549bf4ef722f5e3eb6fadc72d1 2021-11-06T15:01:31Z William Boman william@redwill.se 2021-11-06T15:01:31Z urn:sha1:b5059efeaadecbc96b042d0866e47f2fb3e7dff9 2021-10-14T20:52:23Z William Boman william@redwill.se 2021-10-14T20:52:23Z urn:sha1:a87ea0386110eeeaad47b140b9155abd4c235f64