Dies ist die deutsche MFDoctor-Dokumentation. Technische Bezeichner, CLI-Flags, Regel-IDs und Codebeispiele bleiben unverändert, damit die Inhalte zwischen den Sprachen vollständig kompatibel bleiben. Verwenden Sie den Sprachumschalter für die kanonische englische Fassung.

Standalone per-bundler findings

examples/standalone-findings has four standalone cells — one per supported bundler — that run a real pnpm build with the matching MFDoctor adapter and emit intentional findings.

They are not nested. Nested multi-app orchestration lives in examples/nested-federation (nested docs).

Cell	Bundler	Expected rule IDs
`vite/`	Vite	`config/remote-http-insecure`, `config/remote-manifest-recommended`, `reliability/version-first-offline-remotes`
`webpack/`	Webpack	`shared/version-unsatisfied`, `shared/singleton-risk`
`rspack/`	Rspack	`shared/version-unsatisfied`, `shared/singleton-risk`
`rsbuild/`	Rsbuild	`shared/eager-without-singleton`, `shared/singleton-risk`

pnpm demo:standalone
# or one cell:
pnpm --filter @mfdoctor-standalone/vite build
pnpm --filter @mfdoctor-standalone/webpack build
pnpm --filter @mfdoctor-standalone/rspack build
pnpm --filter @mfdoctor-standalone/rsbuild build

Each cell sets failOn: "never" so the build still completes and writes .mf/doctor/report.json. The demo script asserts the expected rule IDs are present.

For one-rule CLI fixtures, see the one-rule showcase. For a flat multi-bundler red combo, see mixed federation issues.

#Standalone per-bundler findings

Standalone per-bundler findings