Configuration conflict between multiple projects

[theart84]

Thank you for the plugin and the library!
I've encountered an issue. I have two projects that I'm developing simultaneously: a frontend on React and a backend on NestJS. Both projects use biomejs version 1.7.3. Each project has its own configuration files, and they differ slightly. When I run both projects, the config is read from the first project that was started, and the second project uses the schema from the first project. I tried specifying paths in the plugin settings, but that didn't help.
Can you suggest something or is this a bug?
webstorm 2024.1.2 Build #WS-241.15989.105
biomejs plugin 1.1.0

[nico-w]

I'm encountering the same situation.

Having two projects open in Webstorm simultaneously, one of them is showing me unrelated "problems". Good, I found your ticket @theart84 because it made me aware that when I close the other Webstorm those "problems" are gone.

Also tried specifying the paths precisely, but didn't help.

OS: Windows 10 Pro 22H2
WebStorm 2024.1.4
Build #WS-241.17890.13, built on June 4, 2024
BiomeJS Plugin: v1.2.1

I guess it's somewhat a bug, because for me this issue makes biome plugin less usable as I have literally always multiple projects open at the same time - each of them have slightly different config.

[sj-e2digital]

I am also experiencing this problem in a monorepo with multiple biome.json files.

[arnorhs]

My co-worker is also experiencing this issue - but with two windows open for separate projects - each one has a biome.json but their settings is not the same.

As soon as they closed one of the windows, the current window started respecting the biome.json settings

My guess is that there's just a single biome runtime thing going on and it can't handle multiple projects at the same time, yet..

[malyzeli]

I can confirm this still happens in IDEA Ultimate 2024.3.2 with Biome plugin 1.5.5 and @biomejs/biome package 1.9.4.

Doesn't matter if you have multiple projects opened in multiple windows, loaded into single project solution or even multiple biome config roots in a monorepo - it always leads to the same behaviour, that all projects are effectively checked using first loaded config file.