biome-vscode: 🐛 Biome extension using package.json install can't find binary

VS Code version

1.100.2

Extension version

3.0.2

Biome version

1.9.4

Operating system

  • Windows
  • macOS
  • Linux

Description

We have Biome installed within our package.json devDependencies and everything was working fine, but when I upgrade to the new v3 of the biome VSC extension, it gives me the below error:

Image

I followed the instructions here as well: https://biomejs.dev/reference/vscode/#migrating-from-the-2x-extension

Downgrading to v2 does work again.

Steps to reproduce

  1. Upgrade VSC extension
  2. Follow steps here: https://biomejs.dev/reference/vscode/#migrating-from-the-2x-extension
  3. See error

Expected behavior

Biome works

Does this issue occur when using the CLI directly?

Not sure / Not applicable

Link to a minimal reproduction

No response

Logs

2025-05-30 09:16:19.467 [info]  🔒 Started listening for lockfile changes.
2025-05-30 09:16:19.467 [info]  ⚙️ Started listening for configuration changes.
2025-05-30 09:16:20.179 [error] Unable to find the Biome binary.

About this issue

  • Original URL
  • State: open
  • Created a year ago
  • Reactions: 18
  • Comments: 29 (12 by maintainers)

Most upvoted comments

Same issue here!

yeah tbh what’s the point of using the extension if it doesn’t work out of the box

@InsaneNaman this is not a good solution, we will remove biome when it needs to be a configured as dependency with a settings file. Biome is nice as a vs-code extension works out of the box. so when it will need install and config, it’s not worth using it anymore. (so we stay with the old variant, till there is a fix)

this has been bugging me for so long but downgrading works if you have this issue the issue i think is that the version picker does not open in the v3 and there needs to be some documentation upgrade

same here, i tried all pre-release and release versions back from the 3.0.5.

the “first/last” version that works is v2.3.2 none of the pre-releases nor any of of the v3.x versions work.

it’s a normal setup, biome is installed via vscode. not in/via package.json (and we don’t want to add it as project dependency nor do we want to have a biome.json in the project!)

2025-06-05 10:02:38.606 [info]  🔒 Started listening for lockfile changes.
2025-06-05 10:02:38.606 [info]  ⚙️ Started listening for configuration changes.
2025-06-05 10:02:38.792 [error] Unable to find the Biome binary.
Image

by the way: one of the best points of biome, is that it does not need any config!

UPDATE:

when doing a npm install --save-dev --save-exact @biomejs/biome in the project, the version of biome in vscode switches to 1.9.4 and it starts without problem. when uninstalling it form the project the error occurs again.

Image Image

so: does the version 3.x of the biome-vscode plugin not have the biome-binary itself?

Update2

after removing the vscode extension via the uninstall command, installing the specific 2.3.2 version, gives a hint to install biome-binary. doing that works fine. switching to 3.0.5 again: cannot find the biome-binary.

Okay after messing for few,

First install binary - npm install -D -E @biomejs/biome (Dont forget -E, this will freeze the version so your team mates can use the same version)

Basically, binary is not bundled (as mentioned previously) so we have to point the extension to binary. You can open settings.json and point biome lsp to binary.

Image

If I understand this correctly, the desired feature is this one, right? issue #680: Request Support non-root package.json in projects (e.g., frontend subdirectory) I could really use that feature for my latest project 🙂

I have a turbo repo and i am trying to install biome as devDependency at root using npm install -D -E @biomejs/biome but still the latest version of the plugin is unable to find the binary.

Please create a dedicated issue with a reproduction repository.

ok, today i tried again to go to the release version of biome extension 3.0.3 together with the migration guid i found here:https://biomejs.dev/reference/vscode/#migrating-from-the-2x-extension

anyways: the result still cannot find the biome executable after upgrade. going back to 2.3.2, as last working version

yep, downgrade to 2.3.2 works for me.

I started having this issue as well today because my extension just updated to the new 3.0.2 extension in VS Code. This is also what I see in my output.

Image

I’ve tried to set the biome.lsp.bin to the biome location in my roaming/npm folder and that also doesn’t work.

In vs code terminal I am able to call biome --version which is 1.9.4

My project in question has my biome.json at my project root level and that is next to my folder for “frontend” which contains my react app.

If I revert back to the 2.3.2 extension version it works.

If you wouldn’t mind, create a new issue and provide a minimal reproduction repository so we have an idea what your repository looks like

@nhedger, what do you mean exactly by “create a multi root workspace”? Do we just have to move our Biome config into the subfolder, or is there something else? It’s not clear to me from this documentation.

Create a project.code-workspace file at the root of the repo and then add your subfolder to the folders key in that file. The biome.json file should also be located in the subfolder.

Then open the workspace and you’ll see a single workspace folder whose root is your subfolder

I started having this issue as well today because my extension just updated to the new 3.0.2 extension in VS Code. This is also what I see in my output.

Image

I’ve tried to set the biome.lsp.bin to the biome location in my roaming/npm folder and that also doesn’t work.

In vs code terminal I am able to call biome --version which is 1.9.4

My project in question has my biome.json at my project root level and that is next to my folder for “frontend” which contains my react app.

If I revert back to the 2.3.2 extension version it works.

I believe it would, but the LSP session would apply to the whole repo anyway. It would not be scoped to the subfolder

Ah I see the issue. We actually removed the biome.projects setting in the final release because it caused issues.

The recommended course is to create a multi root workspace where the folder is the subfolder that contains your node modules