biome vs-code-extension multi-root-workspace linting

Biome VS Code extension v3 adds multi-root workspace support

Multi-root workspaces, single-file mode, and unsaved file support eliminate the biome.projects config; global Biome install now required for edge cases.

June 9, 2026

Summary

Developers working across multiple projects in one VS Code window no longer need workarounds; isolated Biome instances per folder reduce config collisions. Trade-off: single-file and unsaved-file features require global Biome installation, shifting dependency management upstream.

Why it matters

Implementation verdict

Replaces the deprecated biome.projects setting with native VS Code multi-root folders. Requires Biome installed globally for single-file/unsaved-file modes; the downloader was removed because "package managers handle this better than we could." Worth upgrading now if you use multi-project setups; verify global Biome availability for edge workflows.

Sources

1.Each workspace folder now runs its own independent Biome instance, keeping your projects isolated
2.support for the biome.projects setting has been removed in the final release
3.The extension now fully supports single-file mode
4.this feature requires Biome to be installed globally
5.Managing the lifecycle of downloaded binaries—including updates and cross-platform support is complex. We believe package managers handle this better than we could

Dev Signal

Get briefs like this in your inbox — free, 3x a week.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs