biome-vscode: ๐Ÿ› Pre-Release version does not work with Biome v2 or Biome v1

VS Code version

1.98.2

Extension version

2025.3.151143

Biome version

2.0.0-beta.1 (none displayed in the statusbar)

Operating system

  • Windows
  • macOS
  • Linux

Description

When installing Biome 2.0.0-beta.1 (or Biome 1.9.4) and the pre-release version of the extension as recommended by the Biome 2 beta blog post, the extension does not work correctly.

  • It canโ€™t be registered as a formatter and does not show any linter errors.
  • When trying to use the โ€œBiome: Download CLIโ€ option it does not show 2.0.0-beta.1 as an option. Trying to select any other version throws the error "Cannot find module โ€˜./index-CJAZtKJE.jsโ€™.
  • The icon in the bottom right shows a check-mark but does not show a version and there is no popup asking to install a biome version either. These issues also persisted when switching back to Biome 1.9.4, or doing a reinstall with 1.9.4 and using the pre-release extension. The non pre-release extension seems to work fine with Biome 1.9.4

Steps to reproduce

  1. Add Biome 2.0.0-beta.1 to project (Or Biome 1.9.4)
  2. Install Biome extension in pre-release mode
  3. Try using the extension

Expected behavior

The extension should be able to be registered as a formatter and should show linter error. The Biome: Download CLI option should not throw an error when used. Indicator on bottom right should show a biome version

Does this issue occur when using the CLI directly?

No

Link to a minimal reproduction

https://github.com/sinomsinom/biome-repro-1743157065790 This issue is in any repo I tried (including an empty repo created with the npm create @biomejs/biome-reproduction command) so a repro repo doesnโ€™t seem useful here

Logs

Output:
2025-03-28 10:35:26.190 [info] 





2025-03-28 10:35:26.190 [info] Biome extension 2025.3.151143 activated
2025-03-28 10:35:26.190 [info] Biome extension started
2025-03-28 10:35:26.190 [info] User-facing commands registered
2025-03-28 10:35:26.190 [info] Started listening for lockfile changes
2025-03-28 10:35:26.190 [info] Started listening for configuration changes
2025-03-28 10:35:26.190 [info] Started listening for active text editor changes



biome rage --daemon-logs:
CLI:
  Version:                      2.0.0-beta.1
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           windows

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         unset
  JS_RUNTIME_VERSION:           v22.14.0
  JS_RUNTIME_NAME:              node
  NODE_PACKAGE_MANAGER:         unset

Biome Configuration:
  Status:                       Loaded successfully
  Path:                         C:\Users\<path-to-project>\biome.json
  Formatter enabled:            true
  Linter enabled:               true
  Assist enabled:               true
  VCS enabled:                  false

Workspace:
  Open Documents:               0

Discovering running Biome servers...

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 2
  • Comments: 17 (9 by maintainers)

Most upvoted comments

After doing a git bisect the specific commit to have broken this seems to be https://github.com/biomejs/biome-vscode/commit/602c510201c59d072315769728050c94152889c3