biome-vscode: Extension 'Biome' is configured as formatter but it cannot format 'JavaScript'-Files

When i click configure, no biome is in the list.

I created a fresh new example project:

Installed Biome v2.0.0 in VSCode.

Added settings.json

  "[javascript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "editor.formatOnSave": true,

/example.code.workspace

{
  "folders": [
    {
      "path": "biome-test"
    }
  ]
}

/biome-test/package.json

{
  "name": "biome-test",
  "version": "1.0.0",
  "main": "index.js",
  "devDependencies": {
    "@biomejs/biome": "^1.4.1"
  }
}

/biome-test/biome.json (from biome-hompeage

{
  "$schema": "https://biomejs.dev/schemas/1.4.0/schema.json",
  "organizeImports": {
    "enabled": false
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true
    }
  }
}

/biome-test/index.js

console.log("Hello World!") // without semicolon so `biome check index.js` errors in cli

Restart everything, vscode has no biome.

In command line i can execute:

cd biome-test
./node_modules/.bin/biome check index.js

It shows Checked 1 file(s) in 1031µs Found 2 error(s)

Adding /biome/test/biome.json

  "javascript": {
    "formatter": {
      "semicolons": "asNeeded"
    }
  }

Re-run and it shows Checked 1 file(s) in 932µs

So biome cli works and uses biome.json.

But not in VSCode. Tried nightly too, the same, no biome detected.

VSCode 1.84.2 Biome v2.0.0 Node v18.19.0 Linux Mint 21.2 (Ubuntu jammy)

Let me know, if i can provide more informations.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 16
  • Comments: 52 (6 by maintainers)

Commits related to this issue

Most upvoted comments

I was able to resolve this issue by deleting the cached file on my system folders and reinstalling the Biome extension on VS Code.

  • cd ~/Library/Caches
  • rm -rf dev.biomejs.biome/
  • Open VS Code
  • Uninstall Biome
  • Install Biome
  • Reload VS Code

well, seems like setting eslint and prettier for my monorepo is much easier, thanks

I’m still getting this issue even though I have biome.json in the root of my project and I’ve installed @biomejs/biome globally.

I was able to resolve this issue by deleting the cached file on my system folders and reinstalling the Biome extension on VS Code.

  • cd ~/Library/Caches
  • rm -rf dev.biomejs.biome/
  • Open VS Code
  • Uninstall Biome
  • Install Biome
  • Reload VS Code

Had the SAME issue now, with biome 1.9.4. This solution helped me to fix it.

JFYI For the Windows, the cache folder is located at C:/Users/$your-user/AppData/Local/biomejs Also, make sure that the biome.json is in the root folder of your vscode workspace.

I was able to resolve this issue by deleting the cached file on my system folders and reinstalling the Biome extension on VS Code.

  • cd ~/Library/Caches
  • rm -rf dev.biomejs.biome/
  • Open VS Code
  • Uninstall Biome
  • Install Biome
  • Reload VS Code

I can confirm this is working for me, thanks! 😄

I’m still seeing this in "@biomejs/biome": "^1.8.3". The config file is already on the root (not a monorepo) and @biomejs/biome is installed. 🤔

This snippet is from .vscode/settings.json:

{
  // ...
  "editor.defaultFormatter": "biomejs.biome",
  "[typescript]": {
    "editor.defaultFormatter": "biomejs.biome"
  },
  "[typescriptreact]": {
    "editor.defaultFormatter": "biomejs.biome"
  }
}

+1 Also having this issue all of a sudden. None of the possible solutions in this thread worked for me. I’m on MacOS 14.1, running Biome 1.9.4. This only started AFTER I updated biome to 1.9.4 from 1.9.2. Going back to 1.9.2 did not fix the issue for me unfortunately. Not sure whats up! Super annoying though!

Tried all of the suggestions in this thread and nothing worked.

Then I tried to see if there was a way to install a different version of the extension. I started by installing a pre-release version (2025.5.40952), and boom, that’s all I needed to do.

EDIT: Might be important to note that:

  • I installed Biome via npm
  • I have a biome.json config in my root directory

+1

I was able to resolve this issue by deleting the cached file on my system folders and reinstalling the Biome extension on VS Code.

  • cd ~/Library/Caches
  • rm -rf dev.biomejs.biome/
  • Open VS Code
  • Uninstall Biome
  • Install Biome
  • Reload VS Code

Had the SAME issue now, with biome 1.9.4. This solution helped me to fix it.

JFYI For the Windows, the cache folder is located at C:/Users/$your-user/AppData/Local/biomejs Also, make sure that the biome.json is in the root folder of your vscode workspace.

I can confirm that following those steps fixed the issue for me. Thank you.

This issue should not be closed. I have biome.json in the root of my project and it’s not working

Same issue here - happens rather frequently, very frustrating.

Screenshot 2023-12-15 at 17 32 45

I can still reproduce the issue on the latest version (2025.5.251939).

Can confirm that issue can be resolved by installing version 2025.5.40952 of the extension.

Tip to avoid duplication of the biome.json: create a symbolic link to the file in your workspace folder:

eg if you have a project like:

  • workspace
    • backend
    • frontend
cd workspace
ln -s ./frontend/biome.json .

@nhedger I have created a reproduction repository https://github.com/gabberr/vscode-biome-issue/

EDIT: Sorry, looks like I miss configured lspBin path here. Rechecking…

Had a similar issue, ended up being my user settings JSON in VSCode having the below set:

"editor.defaultFormatter": "esbenp.prettier-vscode"

Removed that, restarted, and all working - if that helps anyone else scratching their heads that has come from prettier 😃

I was able to resolve this by adding .tsx and .ts in files.include option like following:

{
  "files": {
    "include": ["src/**/*.ts", "src/**/*.tsx"],
    "ignoreUnknown": false,
    "ignore": []
  }
}

I had the same issue. The vscode did not recognize biome for the js/ts files. It was a single vscode workspace, however I had the biome.json initially in a subfolder.

I solved it by first moving biome.json to the root folder. I think the extension looks it up from there. Then adjust the configuration .vscode/settings.json :

  "biome.requireConfiguration": false,
  "biome.lspBin": "./biome-test/node_modules/@biomejs/biome/bin/biome",

For WSL, you should try this:

rm -rf ~/.vscode-server/extensions/*

Replace vscode to cursor or windsurf, if you’re using them

I had this issue and it was because I had multiple projects open and not all of them had a biome.json and from the logs it appeared to only be looking at the first project (alphabetized). I saw this in the logs here: dev.biomejs.biome/

To fix this I put my base settings at Users/<my_user>/biome.json since it seems to check there as well. Closing other projects may help too. Hope this helps someone else too.

This is the problem and the ~fix~ workaround! Multiple open projects make the biome extension break if the other projects do not support biome. This is a hefty bug that should be fixed asap. The issue should also not be closed!

none of these solutions work for me on 1.9.4 😕

@DavidMelnychuk please create a new issue with a new reproduction

Thank you for the explanation! My understanding now is that the requirement of the vscode extension is to have the biome.json defined in the root folder.

I am thinking about how the biome works, as is described here. biomejs.dev/guides/big-projects

Does the extension support projects with multiple biome configurations?

If it does, could I create a biome.json file in the workspace root folder, which enables the formatter, linter, autoImport, to satisfy the requirement. Then in the frontend folder, the biome.json with the desired configuration would be defined.

I tried this approach in the repo. The extension started working but was using the biome setting from the root folder and not frontend folder.

The extension no longer requires the biome.json file to be present, but the root of the workspace is still the only place Biome will look for it. Placing a biome.json in a subfolder won’t work unless you run the CLI directly inside that folder.

I had the same outcome as @gabberr when testing this out for our monorepo last week, and was confused, since the CI works great with that setup. (and you def. don’t want a situation where editor and CI is out of sync)

Thank you for the explanation! My understanding now is that the requirement of the vscode extension is to have the biome.json defined in the root folder.

I am thinking about how the biome works, as is described here. https://biomejs.dev/guides/big-projects/

Does the extension support projects with multiple biome configurations?

If it does, could I create a biome.json file in the workspace root folder, which enables the formatter, linter, autoImport, to satisfy the requirement. Then in the frontend folder, the biome.json with the desired configuration would be defined.

I tried this approach in the repo. The extension started working but was using the biome setting from the root folder and not frontend folder.

Is there anything missing in the repro https://github.com/biomejs/biome-vscode/issues/25#issuecomment-1862517467 or something I can try/add to help out? The issue this has the Needs reproduction label.

I was sure we were able to handle unsaved files.

@ematipico Are you suggesting that the steps I posted should result in a successful format instead of seeing the following error message?

Exactly 💯

Extension ‘Biome’ is configured as formatter but it cannot format ‘TypeScript’-files

If yes, should I open a separate issue in this repository with the content of my original comment?

Please open an issue in the main repository. Also, provide the daemon logs by using biome rage --daemon-logs.

It could be very long, so make sure to extract the logs emitted when attempt the formatting.

Moving biome.json to the root folder and then reloading the window, enables the squiggly lines:

Screenshot 2023-12-19 at 16 57 56

Screenshot 2023-12-19 at 17 00 26