monorepo issue

[TheOrdinaryWow]

Assume having following repository structure:

> ls -T -L=1 --git-ignore
apps
├── proxy
├── server
├── server-go
├── web-admin
└── web-user
biome.json
bun.lock
package.json
packages
├── cache
├── config-biome
├── config-typescript
├── ...
tsconfig.json
turbo.json

Crafted using Turborepo. And go application is located in apps/server-go.

But in such cases, golangci-lint failed to initiate, as screenshot below.

Is it a Zed issue or a golangci-lint plugin issue? Thanks.

[christian-gama]

I can confirm the same annoying issue. When working in a mono-repo, non-go files have this error.

[AtomicMegaNerd]

Here is my configuration which I updated for golangci-lint v2:

  "lsp": {
    "golangci-lint": {
      "initialization_options": {
        "command": [
          "golangci-lint",
          "run",
          "--output.json.path=stdout",
          "--issues-exit-code=1",
          "--show-stats=false"
        ]
      }
    },

Linting works on Go files but as others have noted I get errors when opening non-Go files in the project.

[jaymorelli96]

Yeah, same issue.. I tried configuring to skip files or dir but it doesn't work

[AtomicMegaNerd]

Updated the config to match the README:

{
  "lsp": {
    "golangci-lint": {
      "initialization_options": {
        "command": [
          "golangci-lint",
          "run",
          "--output.json.path",
          "stdout",
          "--show-stats=false",
          "--output.text.path="
        ]
      }
    }
  }
}

I am still seeing this bug where it complains about no go files to analyze every time I open a non-Go file in the project. This is making it difficult to weed out actual error diagnostics that are important from these spurious ones from the broken linter extension.

[ajinbaby01]

I have created a PR to the language server that fixes monorepo issues
nametake/golangci-lint-langserver#66

[AtomicMegaNerd]

There has not been a new release of golang-lint-langserver since April 2025. See nametake/golangci-lint-langserver#64.

In Neovim it is possible to work around this by installing a separate plug-in to manage linters that does not rely on these small language servers. Might not be possible here, but it should be noted that this really breaks Zed for Go development :-(

[rreycore]

Are there any updates on this?

[AtomicMegaNerd]

Are there any updates on this?

Not much the Zed devs can do here. Using LSP's for linters like this makes sense (at least initially) as it makes things much easier for the Zed team. Ideally, if this golangci-lint-langserver is abandoned someone with sufficient knowledge and time can fork it and point the Zed nerds in that direction. These LSP's can vary a lot in how much love and maintenance they get over time. Goes with the territory.