biome-vscode: 🐛 Unable to find the Biome binary after extension update

VS Code version

1.100.2

Extension version

3.0.2

Biome version

1.9.4

Operating system

  • Windows
  • macOS
  • Linux

Description

With the new 3.0.X extension versions in VS Code, I now get biome errors that are not very descriptive even with verbose logging turned on.

Image

The only way around this issue for me is to downgrade the extension to 2.3.2. When I downgrade I see

Image

I’ve tried creating the project.code-workspace with my sub folder as the folder name. I’ve tried moving my biome.json from the root to the actual front end folder. Same result for everything that I’ve tried so far.

I’ve deleted node_modules folders, reinstalled biome globally, restarted my computer.

Steps to reproduce

I was going to share my project structure but this also happens in the npm create @biomejs/biome-reproduction project that is generated as well. The images from above are from the reproduction project that is generated.

Expected behavior

I would expect that the newest extension would show the same bundled version of 1.9.4 that is installed.

Does this issue occur when using the CLI directly?

No

Link to a minimal reproduction

No response

Logs

2025-05-30 15:29:40.186 [info]  🔒 Started listening for lockfile changes.
2025-05-30 15:29:40.186 [info]  ⚙️ Started listening for configuration changes.
2025-05-30 15:29:40.573 [error] Unable to find the Biome binary.

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 20 (11 by maintainers)

Most upvoted comments

I’ve added my individual folders for backend and the tests. This should work until I need to get access to the base line files but that isn’t too often.

When i need access to those files frequently, I’ll usually add the root like this:

{
  "folders": [
    { "path": "." , "name": "root"}
  ]
}

Is there some way I can set this up so I don’t need to use a workspace? Maybe this is the moment where I just split my frontend into it’s own project. I’m not sure what industry standards are.

You could install Biome at the root of your repo. Admittedly not ideal when not all your projects use node, but definitely doable.

Dinner on me this weekend! Thank you for your help here. I apologize for being one of those users.

No biggie, and certainly no need to apologize! Happy to help 😃