> For AI agents: the complete documentation index is available at https://mfdoctor.kevinbeier.com/1.0.0/llms.txt, the full documentation bundle is available at https://mfdoctor.kevinbeier.com/1.0.0/llms-full.txt.

# Monorepos

Build each federation app with the mfdoctor plugin so it writes
`.mf/doctor/project.json`. Then run the one-shot workspace gate from the
monorepo root (or scoped roots):

```bash
mfdoctor workspace
mfdoctor workspace apps packages --format terminal,json,sarif
```

That discovers project facts and checks version ranges, providers, singleton
choices, and share scopes across projects. Exit `0` / `1` / `2` match the rest
of the CLI.

## Choose the federation scope

A workspace can be one real federation, a repository of independent fixtures,
or several deliberate federation groups. Keep those cases explicit:

- A real monorepo may use the default workspace gate.
- Independent fixtures should use separate roots/globs, or assign each fixture
  a group in its mfdoctor options.
- Multiple graphs should set the same `federationGroup` on every app in one
  graph and use `--group` when running a focused gate.

```ts
// vite.config.ts / rspack.config.ts / webpack.config.ts
federationDoctor({
  federationGroup: "checkout",
  moduleFederation: mfOptions,
});
```

```bash
mfdoctor federation --workspace --group checkout
```

Projects in different explicit groups are not compared by federation-wide
rules. `workspace` still reports the available group metadata so CI can keep
the gate aligned with the repository topology. Legacy project facts without a
group remain in the ungrouped scope for backwards compatibility.

mfdoctor keeps project display names for v1 reports, but workspace federation uses
a stable application identity based on the workspace-relative app path. This
means two apps with the same package name stay separate. The gate also follows
Node's normal package resolution chain, so pnpm hoists, nested installs, and
workspace links are checked from each app's own context.

If a project report points at a missing root, or duplicate reports share an
identity with different contents, mfdoctor reports partial analysis and exits `2`.
Keep workspace roots scoped to the monorepo and rely on the default ignores for
`node_modules`, build output, caches, and coverage directories.

Manual globs remain available when you need an escape hatch:

```bash
mfdoctor federation "packages/*/.mf/doctor/project.json"
```

Share org policy with a workspace package (or path) and `extends`, see
[policy packs and presets](https://mfdoctor.kevinbeier.com/1.0.0/policy-packs.md). Example fixture:
`fixtures/policy-packs/acme-mfdoctor-policy`.

See [CLI and CI](https://mfdoctor.kevinbeier.com/1.0.0/cli.md) for the reusable GitHub Action.