How to globally apply biome.json to multiple workplaces or projects?

[coolcode]

As official docs mentioned, biome.json has to be put at the root of workplace. Is it possible to make one file biome.json or biome-global.json as a default configuration and apply to multiple workplaces or projects?

[nhedger]

Unfortunately, Biome does not yet handle multiple workspaces.

If all your projects happen to be a part of the same monorepo, I'd suggest putting the biome.json at the root of your monorepo.

[ghandic]

As an alternative you can symlink so its available in both

[j-murata]

Hi @nhedger, I am not sure if this discussion is the right place to post this, but I would like to comment.

When developing in a large monorepo with VSCode, it is often the case that each module has different Lint rules to apply.
I recently tried to use Biome in monorepo and was quite confused because the biome.json configurations in the current working directory (or nearest parent directory) were not reflected on the UI feedback.

Perhaps the eslint.workingDirectories option of vscode-eslint is a similar feature. If such an option is implemented in biome-vscode, more users may be willing to replace ESLint with Biome.

[ematipico]

That wouldn't work because our LSP still doesn't support workspaces.

Ideally, a user wouldn't need any option in VSCode, so users that use other editors can support it too.

Follow biomejs/biome#1573