Did anybody set up eslint flat config with eslint lsp extra?

[Demianeen]

Hi everyone! I used eslint LSP for long time. As for now, it doesn't respect the new eslint flat config format. I tried to debug it within vscode because as far as I know, mason eslint lsp use the vscode eslint lsp. And yeah, it can't find eslint.config.js while .eslintrc.js finds just fine

CleanShot.2024-03-14.at.14.49.13-converted.mp4

I managed to get it to work with vscode by adding "eslint.experimental.useFlatConfig": true to vscode settings json file. I added the same thing to the eslint initialization options:

return {
  'neovim/nvim-lspconfig',
  -- other settings removed for brevity
  opts = {
    ---@type lspconfig.options
    servers = {
      eslint = {
        settings = {
          -- helps eslint find the eslintrc when it's placed in a subfolder instead of the cwd root
          workingDirectories = { mode = 'auto' },
          experimental = {
            -- allows to use flat config format
            useFlatConfig = true,
          },
        }
      },
    },
  }
}

But it doesn't work for whatever reason. Has anyone configured the eslint flat config to work with eslint LSP or with eslint_d?

P.S. Does anyone know any plugin that helps to see debug logs per each LSP?

[madflow]

I did a quick test, and it just works. I use the "extras.linting.eslint" rule. Maybe you could be more speficic what is "not working"?

[Demianeen]

Hi yeah, it does not give any listing errors, or any errors, even in lsp log, except for the warning about missing action workspace/didChangeWorkspaceFolders. But it is always there because it is not VSCode.

CleanShot.2024-03-16.at.10.21.01-converted.mp4

Also, could you let me know if you tried with flat config?

It should look like this:

module.exports = [
...
]

Sorry to ask, but I had a few other people who assumed I was talking about the older eslint config format.

[madflow]

Well I put

export default [
    {
        files: ["**/*.js"],
        rules: {
            "semi": "error",
            "no-unused-vars": "error"
        }  
    }
];

in a eslint.config.js file and it worked. I just did what was desribed here: https://eslint.org/blog/2022/08/new-config-system-part-2/

In the video you posted is "hard" parse error by eslint. This could be the problem, when eslint does an hard exit. Maybe move the file in question (tsconfig.base.json) and try again.

[Demianeen]

Thanks @madflow! Thanks to you I figured out that the issue was the eslint config itself. It is strange because it worked fine with the same configuration with .eslintrc 😅

It is also super strange that there were no error in lsp debug log about error with starting eslint

[sondrej]

Related issue with latest version of vscode-langservers-extracted: microsoft/vscode-eslint#1839
After updating this through Mason from 4.8.0 to 4.10.0 I no longer get diagnostics/errors from eslint. Apparently workingDirectories = { mode = 'auto' }, seems to be broken in latest release.

[sondrej]

Only workaround I've found so far is to downgrade eslint-lsp to version 4.8.0:
: MasonInstall eslint-lsp@4.8.0

[qadzifi-baskit]

This works for me, wondering why my neovim eslint doesn't show anything (trouble, error, suggestion, or something) and with this now it works

[gtarsia]

I spent two hours before finding the solution by @Demianeen. Wondering what's the best solution for this since it's been a month now.

Maybe lazyvim should have a warning in the readme (I can help with this)? Or mention this to Mason devs so they can use 4.8.0 as latest? Not sure what's the best way to spare lazyvim users this problems since there is no error message to figure out.

[kesor]

Yesterday lspconfig broke it with neovim/nvim-lspconfig#3183