Support for Multiple Projects in a Single Workspace

[lucaschultz]

Hi,

I saw in this PR that support for multiple projects in one workspace is coming soon. I followed the instructions in the documentation by adding

"biome.projects": [
  {
    "path": "apps/reference-api"
  }
]

to my .vscode/settings.json and the mono repo root, and I installed the pre-release version of the extension, but it didn't work. My folder structure is:

.
├── .vscode
│   └── settings.json
├── apps
│   └── reference-api
│       ├── biome.jsonc
│       ├── package.json
│       ├── src
│       └── tsconfig.json
├── biome.jsonc
├── package.json
├── packages
│   └── config
│       └── tsconfig
├── pnpm-lock.yaml
├── pnpm-workspace.yaml
└── turbo.json

In apps/reference-api/biome.jsonc, I extend from biome.jsonc but disable a rule:

{
  "$schema": "https://biomejs.dev/schemas/1.9.4/schema.json",
  "extends": ["../../biome.jsonc"],
  "linter": {
    "rules": {
      "suspicious": {
        "noExplicitAny": {
          "level": "off"
        }
      }
    }
  }
}

This setup works with the CLI, but not with the VSCode extension. Am I doing something wrong, or is this feature not yet supported in the pre-release version of the VSCode extension?

[nhedger]

Hey,

I would expect this to work.

Are you not getting the diagnostics at all, or is it that the config file is not being used ?

Anyway, would you mind creating a reproduction repo so we can try and reproduce ? You can use npm create @biomejs/biome-reproduction@latest

[chiragmRoado]

@nhedger Similar issue with my setup as well.

Here's the setup overview:

"biome.projects": [
  {
    "path": "app1"
  },
  {
    "path": "app2"
   }
]

.
├── biome.json (Root in Working Directory)
├── app1
│       ├── biome.json
│       ├── package.json
│       ├── src
│       └── tsconfig.json
├── app2
│       ├── biome.json
│       ├── package.json
│       ├── src
│       └── tsconfig.json
├── app3
│       ├── biome.json
│       ├── package.json
│       ├── src
│       └── tsconfig.json

Each application is structured as a separate repository, with its own biome.json configuration file to handle unique linting and formatting rules.

Biome plugin does not appear to recognize or apply the individual configurations for each repository correctly. Instead, it crashes unless a single biome.json is placed at the root level. While this workaround enables the plugin to function, it disregards the specific rules defined in each repository, which is not ideal.

The only alternative right now is to open each project in a separate window, but that's not ideal given how our projects are structured.

[ematipico]

As mentioned here #426 (comment), we would need a reproduction. A minimal one.