Enable biome only when biome.json is present gives error

[kjvdven]

I followed the docs to only Enable biome only when biome.json is present. And I added the following code to my config.

"lsp": {
    "biome": {
      "settings": {
        "require_config_file": true
      }
    },
}

Now I expected Biome to be disabled on projects without a config file.

But instead I get the following error;

Language server error: biome

biome.json is not found but require_config_file is true
-- stderr--

[luckydye]

It's a limitation of zed extensions at this time. There is currently no other way of canceling the server start, except by throwing an error.

If there if a better approach, PRs are welcome.

Otherwise, if you want to actually only enable the language_server in specific projects, follow this guide:
https://biomejs.dev/reference/zed/#project-based-configuration

[silvenon]

The require_config_file option lead me to believe that it's a solution to running the extension only in projects that use Biome, so maybe it would be better to withdraw this feature until it's actually possible to automatically not run the extension in projects where it's not installed.

[jbergstroem]

It's a limitation of zed extensions at this time. There is currently no other way of canceling the server start, except by throwing an error.

Is there a tracking issue for this?

[luckydye]

It's a limitation of zed extensions at this time. There is currently no other way of canceling the server start, except by throwing an error.

Is there a tracking issue for this?

I don't think so.

[kjvdven]

I did make an issue on the Zed repository.
zed-industries/zed#19589

[ematipico]

Have you tried requireConfigFile?

[silvenon]

Have you tried requireConfigFile?

Instead of require_config_file? It doesn't prevent Biome from running in a non-Biome project, but unlike require_config_file something different happens — the extension manages to run Biome even though Biome is not installed that workspace. With require_config_file the extension itself fails in a non-Biome project 🤔

[emigdio821]

I can confirm that this is still an issue in the latest version (0.1.4), I tried using requireConfigFile and require_config_file. 😢

[oca159]

can someone provide an update on this? still happening to me in the latest version of zed

[chulkilee]

Can we make biome zed plugin no-op when the condition is met, instead shutting down it with error?

[silvenon]

Note

Workaround: just in case someone wasn't aware of this, in global settings I do "language_servers": ["!biome", "..."], and in projects with Biome I add local settings with "language_servers": ["..."]. This works fine for me.

I just wish that in the meantime there was something to track 😕 Biome believes this to be a Zed issue, unable to fix from within the extension, and Zed appears to have kicked it back to Biome.

I just read the upstream issue again, zed-industries/zed#19589, and they seem be hinting the same thing — enabling Biome per-project. But it's bad developer experience when switching between branches that have implemented Biome and those that don't.

It feels like that recommendation was made from the implementation perspective, not usage perspective. I would like the no-op implementation as suggested above.

[kucho]

I'm on the latest preview and no longer see the error!

[dmythro]

My problem with this issue is: when I open a project (where biome.json exists and all good) — I get no errors at first, but then suddenly with time this error occurs. This is very odd.