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
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.
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
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.