Environment information
Below are the details of my local development environment, but the same issue can also be reproduced on Linux (Ubuntu 24.04 LTS).
Details
CLI:
Version: 2.4.4
Color support: true
Platform:
CPU Architecture: aarch64
OS: macos
Environment:
BIOME_LOG_PATH: unset
BIOME_LOG_PREFIX_NAME: unset
BIOME_LOG_LEVEL: unset
BIOME_LOG_KIND: unset
BIOME_CONFIG_PATH: unset
BIOME_THREADS: unset
BIOME_WATCHER_KIND: unset
BIOME_WATCHER_POLLING_INTERVAL: unset
NO_COLOR: unset
TERM: xterm-256color
JS_RUNTIME_VERSION: v24.13.1
JS_RUNTIME_NAME: node
NODE_PACKAGE_MANAGER: pnpm/10.30.1
Biome Configuration:
Status: Loaded successfully
Path: biome.json
Formatter enabled: true
Linter enabled: true
Assist enabled: true
VCS enabled: true
HTML full support enabled: unset
Workspace:
Open Documents: 0
What happened?
Starting with Biome 2.4.0, if the Biome config is not in the workspace root and configurationPath in VSCode is set to a relative path, it will not work correctly: the LSP server will be unable to communicate properly with VSCode and will not register as a formatter.
The git repo below can be cloned directly to reproduce the issue
https://github.com/birdhackor/biome_bug
For the git repo above, as long as you downgrade Biome to version 2.3.15 or earlier in the frontend folder, everything returns to normal.
Aside from downgrading, when using version 2.4.4 you can also restore normal behavior by setting biome.configurationPath in .vscode/settings.json to an absolute path.
Not sure if it's related to #7138 (comment)
Expected result
Versions 2.4.0 and above should work correctly with VS Code.
Code of Conduct
Environment information
Below are the details of my local development environment, but the same issue can also be reproduced on Linux (Ubuntu 24.04 LTS).
Details
What happened?
Starting with Biome 2.4.0, if the Biome config is not in the workspace root and configurationPath in VSCode is set to a relative path, it will not work correctly: the LSP server will be unable to communicate properly with VSCode and will not register as a formatter.
The git repo below can be cloned directly to reproduce the issue
https://github.com/birdhackor/biome_bug
For the git repo above, as long as you downgrade Biome to version 2.3.15 or earlier in the frontend folder, everything returns to normal.
Aside from downgrading, when using version 2.4.4 you can also restore normal behavior by setting
biome.configurationPathin.vscode/settings.jsonto an absolute path.Not sure if it's related to #7138 (comment)
Expected result
Versions 2.4.0 and above should work correctly with VS Code.
Code of Conduct