For AI agents: the complete documentation index is available at https://mfdoctor.kevinbeier.com/llms.txt, the full documentation bundle is available at https://mfdoctor.kevinbeier.com/llms-full.txt, and this page is available as Markdown at https://mfdoctor.kevinbeier.com/standalone-findings.md.
MFDoctor
  • English
  • 1.1.0

      • Standalone per-bundler findings

      examples/standalone-findings has four standalone cells — one per supported bundler — that run a real vp run 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).

      CellBundlerExpected rule IDs
      vite/Viteconfig/remote-http-insecure, config/remote-manifest-recommended, reliability/version-first-offline-remotes
      webpack/Webpackshared/version-unsatisfied, shared/singleton-risk
      rspack/Rspackshared/version-unsatisfied, shared/singleton-risk
      rsbuild/Rsbuildshared/eager-without-singleton, shared/singleton-risk
      vp run demo:standalone
# or one cell:
vp run --filter @mfdoctor-standalone/vite build
vp run --filter @mfdoctor-standalone/webpack build
vp run --filter @mfdoctor-standalone/rspack build
vp run --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.