ESLint stops functioning after updating `vscode-langservers-extracted` to 4.10.0

[mguellsegarra]

ESLint stops functioning after updating `vscode-langservers-extracted` to 4.10.0

[when-harry-met-sally]

MasonInstall [email protected] worked for me.

[9mm]

Im also encountering this, and vscode-langservers-extracted has no issues enabled to even report the issue. I cant really imagine stack overflow is the best place to put bug reports. maybe @hrsh7th can be summoned?

@jackpinto @mguellsegarra what behavior are you experiencing? For me, the diagnostics just dont show at all, however if i run EslintFixAll it DOES work, so i know lspconfig/eslint is reading the proper project eslintrc file etc, it just simply will not show any diagnostics. theres also no errors in LspLog, and all of that is working properly it seems

[mguellsegarra]

Just wanted to update everyone—I've opened a PR addressing the issue we've been discussing. You can follow the conversation here.

[heygarrett]

Workaround:

1. Uninstall eslint-lsp with Mason
2. npm install --global [email protected]
3. Add require("lspconfig").eslint.setup({}) to your config

[justinmk]

Thanks for your report. The configs in this repo are unsupported and provided only as a starting point. We depend on users (like you) to troubleshoot issues with their specific LSP setups and send improvements.

If you have a usage question, try asking it at:

• https://github.com/neovim/neovim/discussions
• https://vi.stackexchange.com/

If you found a bug in the core Nvim vim.lsp module (not part of this repo), the best way to get it fixed is to report to Nvim (not nvim-lspconfig) with:

• steps to reproduce it without the particular LSP server and other factors particular to your environment
• (optional, but very helpful): by adding a failing test case to lsp_spec.lua, which has code to setup a fake LSP server to simulate various scenarios

[mguellsegarra]

@jackpinto @mguellsegarra what behavior are you experiencing?

Diagnostics don't show up, sadly. I ended up putting all my share/nvim/ folder into a git repo for controlling all the Mason updates, because there's no way to lock versions. Sticking to 4.8.0 for the moment, until I have time to investigate what happened.

[mguellsegarra]

@justinmk hey, I appreciate your time and apologize for mistakenly posting this issue in the incorrect repo. Will try to fix it and report it properly. Thanks!

[jackpinto]

@mguellsegarra

Do you have any clues on how to fix the setup for version 4.10?

I am looking, but I haven't found anything so far.

[jackpinto]

@9mm same here, it only doesn't show the diagnostics.

[adibfirman]

Installing like @when-harry-met-sally suggested it, works for me
oh config how do I make sure Mason will install with the specific version?