Replies: 4 comments 1 reply
-
Hey @sairion, Thanks for opening this issue. I can't speak for everyone, but this is definitely something I'd like to see us support. I'll move this issue to the https://github.com/biomejs/biome repository because that's where the logic should be implemented. |
Beta Was this translation helpful? Give feedback.
-
We also use a monorepo, and we're blocked due to this issue as well. We (would like to) have a biome.json at the repo root, which vscode & other extensions will load |
Beta Was this translation helpful? Give feedback.
-
Our particular case also favours the introduction of more monorepo-friendly features such as:
I still didn't read all the related issues, discussions, rfcs, etc. But I suspect that there is some work being performed on this front. What I don't know yet is if it will cover these specific issues. In case the ongoing work is covering a different set of issues, I'd like to discuss with the core developers if I can contribute code to solve the issues I presented. |
Beta Was this translation helpful? Give feedback.
-
I am going to close this discussion, people can help and track progresses here: #2228 |
Beta Was this translation helpful? Give feedback.
-
It seems Biome VS Code extension only uses
biome.json
at the workspace root, not 'the most adjacent'biome.json
from the source which it lints, formats, etc. (I believe it is also Rome VS Code extension's behavior, after seeing rome/tools#4206)I'd like to know if support for monorepo (or, multiple
biome.json
in workspaces) is going to happen :)Beta Was this translation helpful? Give feedback.
All reactions