Member projects

Members are normal Beskid projects with their own Project.proj. The workspace adds labels and shared policy—not a second hidden build system.

Member labels

member "app" { path = "apps/main" } means tooling can target app while resolving paths relative to the workspace root. Exact CLI flags: --workspace-member on commands that support project resolution (see command reference).

Typical layout

repo/
├── Workspace.proj
├── apps/
│   └── main/
│       ├── Project.proj
│       └── Src/
└── libs/
    └── shared/
        ├── Project.proj
        └── Src/

Path dependencies between members often use relative path = "../../libs/shared" edges—keep them boring and explicit.

Editor experience

Open the workspace root folder in VS Code so LSP sees Workspace.proj. Opening only a nested member folder works until it does not—usually when cross-member imports confuse discovery.

Next

Dependency cycles