Ability to configure workspace behaviour

[jonnyroutley]

Hey there,

I'm trying to debug various performance issues with Biome in my IDE, and came across something that probably isn't the major culprit but caught my attention. I work with a monorepo with many packages but only one biome config file, something like this:

.
├── packages
│   ├── foo
│   ├── bar
│   ├── baz
│   ├── ...
│   ├── ...
│   └── qux
biome.jsonc

I've read in the v3 docs for this extension that a new biome instance is automatically created for each workspace root - in my case 17 instances. That feels like overkill when they all share the same config?

Any thoughts appreciated! Thanks

[nhedger]

Hey @jonnyroutley, are all your packages part of the same npm workspace ? If so, you can install Biome at the root of your monorepo and open a single workspace folder (at the root of the repo). This would spawn a single biome instance configured by your root biome.json config.

[jonnyroutley]

They're all part of one pnpm workspace, with biome installed at the root. I thought this might be working off of my .code-workspace file? Which sets up all all the packages as different folders (incidentally so the Jest extension works properly)

[nhedger]

If you open a .code-workspace, this would indeed create one instance per workspace folder, I'm afraid there's not way around it currently. This is because you may have different versions of Biome in various workspace folders (which may not necessarily belong to the same repo).

[jonnyroutley]

Thanks, I'll have a play around and see if I can get rid of the workspace file. Cheers :)

[fronterior]

Just chiming in here to share a related discussion I opened recently: #802 .
I built an unofficial plugin called Biome Monorepo that allows you to open and work with the monorepo root as a single workspace.
It also addresses the limitation mentioned above by mapping each subproject to its own Biome binary.
If this sounds relevant, I'd love to hear your thoughts!