biome-vscode: 🐛 Cannot find installed biome binary
VS Code version
1.91.1
Extension version
v2024.8.301002
Biome version
1.8.3
Operating system
- Windows
- macOS
- Linux
Description
Steps to reproduce
I simply added this:
yarn add --dev @biomejs/biome
npx biome init
I also installed the prerelease version of this extension.
Expected behavior
Biome binary from node modules should be found.
Does this issue occur when using the CLI directly?
Not sure / Not applicable
Link to a minimal reproduction
No response
Logs
2024-09-09 10:31:51.668 [info] Biome extension activated
2024-09-09 10:32:54.370 [error] Failed to start Biome extension
2024-09-09 10:32:54.370 [info] Biome extension started
2024-09-09 10:32:54.370 [info] User-facing commands registered
2024-09-09 10:32:54.370 [info] Started listening for lockfile changes
2024-09-09 10:32:54.370 [info] Started listening for configuration changes
2024-09-09 10:32:54.370 [info] Started listening for active text editor changes
2024-09-09 10:32:57.702 [info]
2024-09-09 10:32:57.702 [info] Biome extension activated
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 19 (2 by maintainers)
@nhedger I am still facing this problem on
3.0.3However when I do
biome rageI managed to fix it by installing biome as global package on windows 11
npm i -g @biomejs/biomeI use M1 chip and I managed to fix it by installing biome cli in my project
pnpm i -D @biomejs/cli-darwin-arm64@1.9.4By default when i usepnpm i @biomejs/biome, it will install @biomejs/cli-darwin-x64 as cli instead of@biomejs/cli-darwin-arm64I had the same problem with Mac M1. I am using fnm to manage node env, and I didn’t want to install it globally. I set the path manually in VSCode settings. I hope it helps.
.vscode/settings.json
I’m having this same issue under WSL with biome being installed with pnpm. It doesn’t help to install biome globally either (and that’s not really a fix either).
For me, updating to biome v2.0.6 and restarting VSCode worked on Windows + WSL.
Update to v3
the same here, using win11 and npm, global installation did not solve it.
besides that I am getting this error when trying to run the check.
thanks for this @eliezra236 . it worked for me on linux too
We released v3. If it doesn’t fix it for you, please open a fresh issue with a reproduction repository
This seems to work, thanks!