Closed Drew-Daniels closed 2 months ago
you upgrade eslint version then you got it not work. so what's the problem of this plugin ?
The problem is that this plugin doesn't work when I upgrade eslint,so I think there might need to be changes so that it does?
@Drew-Daniels Thanks for reporting this. I have this issue too, and downgrading the eslint lang server to 4.8.0 worked for me too.
@dyllandry Totally! Glad it helped. Also, FWIW, I was able to upgrade eslint
to the latest version and get LSP diagnositics as expected by updating my LSP config to:
require("mason-lspconfig").setup({
ensure_installed = {
-- ...
"eslint",
-- ...
},
})
-- ...
lspconfig.eslint.setup({
capabilities = capabilities,
settings = {
workingDirectories = { mode = "auto" },
experimental = {
useFlatConfig = false,
}
},
})
My guess is that this was silently failing when eslint v4.9.0
was used, but after that, I started getting errors logged in neovim about the change from nested to flat configs, at which point I updated my config to the above 🤷🏻
Just chiming in here to report another incidence of this—eslint
did not work for me using v4.10.0
.
To solve, run :MasonInstall eslint-lsp@4.8.0
.
Description
Thanks for this plugin! I use this for development everyday.
I use mason.nvim and mason-lspconfig.nvim to manage my language servers.
I have been able to update the eslint language server consistently, up until the v4.9.0 release.
eslint.config.mjs
:When I upgrade to
v4.9.0
, and open a JavaScript file, I can see that theeslint
server is running, but I stop gettingeslint
warnings and errors.When I downgrade back to
v4.8.0
, and see I start gettingeslint
warnings and errors again:nvim-lspconfig
version as inlazy-lock.json
: