using extension with projects with slightly different Biome versions (2.0.4 vs. 2.0.6 etc.)

[pirxpilot]

I am probably missing some config trick here: I have several project I am using Biome with. They all list specific version of Biome as a dev dependency in package.json. When I open them in zed with biome-zed extension enabled in most cases I see: The configuration file has errors. Biome will report only parsing errors until the configuration is fixed. error - since extension will only accept the config for the version the matches exactly the version distributed with the extension (or at least this is what I think is the cause of the error). Is there any way to tell the extension to use the version of Biome configured in package.json? Any other ideas how to deal with it?
The extension when it works is a great timesaver. Thanks!

[ematipico]

Hey!

At first glance, it seems that the extension can't find the binary to execute. When it doesn't, it falls back to the "built-in" version, which is installed from npm.

How's the structure of your projects? Did you identify a particular project that triggers the problem? Have you tried the CLI? Or did you check the logs for more information?

[pirxpilot]

You are absolutely right: the extension could not locate the biome binary. I uninstalled globally installed biome and it seemed to help with all the project with a typical structure (./node_modules/.bin/biome in the root of the project).
For a more complicated setup I added zed project settings like this:

{
  "lsp": {
    "biome": {
      "binary": {
        "path": "./meta/node_modules/.bin/biome",
        "arguments": ["lsp-proxy"]
      }
    }
  }
}

and everything seems to be working OK now.
Thanks again for the help.