biome-vscode: 🐛 Failed to install Biome binary on WSL, Could not find Biome 1.9.4 for your platform.
VS Code version
1.95.0-insider
Extension version
v2024.10.131712 (pre-release)
Biome version
1.9.4
Operating system
- Windows
- macOS
- Linux
Description
I can’t install Biome globally because it keeps giving me the error “Could not find Biome 1.9.4 for your platform.”
My System Information:
Ubuntu 24.04 on WSL2 on Windows 11 Pro (24H4)
uname -a output:
Linux Vivobook 5.15.153.1-microsoft-standard-WSL2 #1 SMP Fri Mar 29 23:14:13 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Steps to reproduce
- A popup pops up and asks if I want to install Biome globally
- I click “Install Biome” (somehow it says so)
- I choose the right version (1.9.4 latest)
- And the error “Could not find Biome 1.9.4 for your platform.”
Expected behavior
I have installed Biome globally and am happily using it
Does this issue occur when using the CLI directly?
No
Link to a minimal reproduction
No response
Logs
2024-10-20 07:30:27.974 [info] Biome extension 2024.10.131712 activated
2024-10-20 07:30:29.102 [error] Could not find the Biome binary
2024-10-20 07:30:39.450 [error] Failed to start Biome extension
2024-10-20 07:30:39.450 [info] Biome extension started
2024-10-20 07:30:39.451 [info] User-facing commands registered
2024-10-20 07:30:39.451 [info] Started listening for lockfile changes
2024-10-20 07:30:39.451 [info] Started listening for configuration changes
2024-10-20 07:30:39.451 [info] Started listening for active text editor changes
2024-10-20 07:35:26.183 [error] Could not find the Biome binary
2024-10-20 07:35:31.948 [error] Failed to start Biome extension
2024-10-20 07:35:31.948 [info] Biome extension restarted
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 24 (17 by maintainers)
Commits related to this issue
- fix: incorrect asset name closes #404 — committed to shulaoda/biome-vscode by nhedger 2 years ago
Fixed by reinstalling Windows
I chuckled 😁. I’ve published a new pre-release that includes the fix already, btw
the issue is that the extension checks for repository assets that starts with
cli-but they start withbiome-If you open the extension dist and change
to
( line 31993 on prerelease 2024.12.22126 )
and reload extensions, it downloads it fine
I’m not joking
this issue happened on my computer too, this is my environment:
I found a possible reason is that the platformIdentifier variable of this extenstion does not match the biomejs downloaded binary package.
The platformIdentifier always points to “linux-x64-musl” if the platform equals “linux”, but pnpm downloads the “@biomejs/cli-linux-x64” package on the Ubuntu based on the it’s package.json config: {“libc”: [“glibc”]} .
I’d appreciate it if you could refrain from pinging me directly when I haven’t yet interacted with an issue. I’ll get to it when I have time.
@nhedger