🐛 Biome plugin does not work when extending a configuration

[mjakl]

IDE and version

WebStorm 2025.2

Extension version

1.10.0

Biome version

2.1.4

Operating system

• Windows
• macOS
• Linux

Description

I've a shared biome.json configuration that I import using extends:

{
  "$schema": "https://biomejs.dev/schemas/2.1.4/schema.json",
  "extends": ["@mjakl/core/biome.json"],
  "files": {
    "includes": ["**", "!**/*.css", "!static/vendor/**"]
  }
}

This works fine with biome on the CLI (eg. bun biome check . or bun biome check --write --unsafe . etc.).

In WebStorm, I installed the latest Biome plugin, and it fails to work no matter what I set in the configuration options. I've tried with and without LSP, I've restarted WebStorm several times. I've tried to manually run the Biome commands (fixes and sort imports). It all fails silently - for running the commands manually I get a success message in the notifications.

When I replace the biome.json with the version I extend from it works as advertised:

{
  "$schema": "https://biomejs.dev/schemas/2.1.4/schema.json",
  "vcs": {
    "enabled": true,
    "clientKind": "git",
    "useIgnoreFile": true
  },
  "files": {
    "ignoreUnknown": false,
    "includes": ["**", "!**/*.css", "!static/vendor/**"]
  },
  "formatter": {
    "enabled": true,
    "indentStyle": "space"
  },
  "linter": {
    "enabled": true,
    "rules": {
      "recommended": true,
      "correctness": {
        "noUnusedImports": "error"
      }
    }
  },
  "javascript": {
    "formatter": {}
  },
  "assist": {
    "enabled": true,
    "actions": {
      "source": {
        "organizeImports": "on"
      }
    }
  }
}

(The only difference is the files.includes which is not present in the extended biome.json).

I can only assume that the plugin version of Biome somehow isn't able to read the extended biome.json or doesn't support the feature at all.

I hope it's ok to skip the reproduction repository as this is about the plugin configuration, not the functionality itself. If needed I'll provide something... .

Steps to reproduce

Create a biome.json that uses extends. The Biome plugin stops working.

Expected behavior

I would be great when the CLI and plugin version of Biome work exactly the same.

Does this issue occur when using the CLI directly?

No

Link to a minimal reproduction

No response

[mnahkies]

I suspect I'm experiencing this issue as well

[jmory]

In my case it works when manually configuring the plugin ("Manual Biome configuration"), but fails when automatically configuring the plugin ("Automatic Biome configuration").