Biome settings file doesn't seem to work

[coolemur]

In zed settings.json I have:

{
	"lsp": {
		"biome": {
			"settings": {
				"config_path": "./biome.json"
			}
		}
	}
}

In biome.json:

{
	"$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",

	"linter": {
		"enabled": true,
		"rules": {
			"recommended": true,
			"complexity": {
				"noBannedTypes": "warn",
				"noForEach": "warn"
			}
		}
	}
}

Rules doesn't seem to work, it still shows as errors instead of warnings.

(I have no biome config in project, so I expect this global config to work when I set it in config_path)

---

Zed: v0.187.9 (Zed)
OS: macOS 15.3.2
Memory: 16 GiB
Architecture: aarch64

[ematipico]

Have you tried with an absolute path? Since your project doesn't have a configuration, maybe the extension is looking for the configuration inside the project, since it's a relative path

[coolemur]

@ematipico yes, I tried with absolute paths:

"config_path": "~/.config/zed/biome.json"

and

"config_path": "/Users/Mantas/.config/zed/biome.json"

Restarted language server after each change

Same result

[ematipico]

I think the configuration doesn't work with Biome v1.9.4. cc @siketyan Am I correct?

[coolemur]

Which version of Biome it should work with @ematipico ? I can test it to make sure if this is the case

[siketyan]

The extension does support config_path for v1.9.4, but it's possible that the is_biome_v1 logic added in #77 is broken on some environments.

[siketyan]

Could you try downgrading the extension to v0.1.4?

[coolemur]

Installed Biome extension v0.1.4 . Tried it with Biome v1.9.4. Using absolute path of biome.json. It still didn't work.

[coolemur]

Findings:

• Setting config path env variable for biome and running lint does not work
  BIOME_CONFIG_PATH=/Users/Mantas/.config/biome.json biome lint test.ts

• Running command with config-path flag works
  biome lint test.ts --config-path=/Users/Mantas/.config/biome.json

From biome docs: "Biome commands support using the --config-path option and the BIOME_CONFIG_PATH environment variable."

So this issue might originate from biome command itself.

Created: biomejs/biome#6160