🐛 multi-root workspace - setting used in pre-release version, but default settings are applied instead

[luarmr]

VS Code version

Cursor

Extension version

2025.5.251939

Biome version

1.9.4

Operating system

• Windows
• macOS
• Linux

Description

Biome 1.9.3 correctly picks up biome.json in subfolders when using a multi-root workspace in VSCode, as recommended here.
Biome 1.9.4 no longer respects these configurations (biome.json in a subfolder), leading to incorrect linting/formatting.

This problem is also observer in the oficial release version, not only in pre-release. Since looks related with biomejs package and not with the extension per se.

Steps to reproduce

1. Clone this reproduction repo https://github.com/luarmr/biome-issue-reproduction
2. run npm install in both folders
3. Open both subfolders as a multi-root workspace in VSCode using the provided code-workspace file in the repo
4. Compare behavior between 1.9.3 and 1.9.4. You will see that one show the error that should be ignored by "noUnusedTemplateLiteral": "off" in the file test.js

Expected behavior

Biome uses the biome.json in each subfolder.

Does this issue occur when using the CLI directly?

No

Link to a minimal reproduction

https://github.com/luarmr/biome-issue-reproduction

Logs

[luarmr]

This comment also apply here:
#547 (comment)

Workaround: downgrade to 1.9.3 of biomejs dependency in your project.

[lumpinif]

It happened to me too!

tl;dr:

for biome corrupting improts on file save add this in project.code-workspace config:

{
  "folders": [
    {
      "name": "root",
      "path": "."
    },
    {...others}
  ],
  "settings": {
    "biome.enabled": false,  (only disable for root, not affecting apps and packages)
  }
}

for biome is not using correct config in monorepo:

including root folder in workspace too. (might still not working as expected)

Some context here:

After a long period of frustratedly struggling with all kinds of bugging issues in biomejs-vscode extension, I have figured out a workaround for this if you are also including root in project.code-workspace config, in which case, I suspect that Biome extension is buggy for this situation as it might running duplicated processes at once which causes some sort of race conditions that might also not only causing biome configs not taken in effect correctly but also corrupting imports when enable auto sorting on file save like:

"editor.codeActionsOnSave": {
    "source.organizeImports.biome": "explicit"
 },

.

and of cause...
I really wish biome-vscode extension can be as better and good as biomejs/biome is, otherwise it is distancing the whole biome thing from me just because the bad editor developing experience. 😔

[vchirikov]

after updating to biome v2, extension (3.0.3) just messed up the subfolder configuration settings.
nothing is working properly, nor biome.configurationPath nor biome.lsp.configurationPath, I even tried set BIOME_CONFIG_PATH, but extension just broken.

[paul-sachs]

I can also confirm this is the case. Looking through the code, I don't even see any references to configurationPath at all, I suspect it got lost somewhere in history. There's even a test workspace located at ./test/fixtures/custom-config that reflects the problem. I'll try to dig in and see if I can fix it.