export default defineNuxtConfig({
  modules: ["vite-doctor/nuxt"],
});

pnpm nuxt doctor

Use pnpm vite-doctor . --max-warnings 0 in CI when the exit code must fail the job. Nuxt's host-command fallback currently prints the report but can swallow the shim's nonzero status. Use pnpm vite-doctor migrate ... for migration checks that also need a reliable exit code.

The standalone CLI also works for Nuxt one-off runs, CI fallback, or monorepo scans.

Workflow

Use vite-doctor . --changed --format agent for uncommitted work. Use vite-doctor . --since <base-ref> --format agent for a committed branch or pull request. Run Doctor without either scope flag when Git is unavailable or the user asks for a project audit.
Read status, scope, and every Diagnostic's code, message, remediation, confidence, relative location, evidence, and optional edit plan.
Work only on Diagnostics owned by the requested change. Do not widen the task to unrelated findings.
Apply the smallest fix that satisfies the remediation and preserves project conventions. Treat structured edit plans as proposed edits, not permission to skip review.
Replace the <rule> item in commandArgs.verify with the Diagnostic's Rule ID. Execute the first array item with the remaining items as literal arguments, without a shell, from project.cwd.
Execute commandArgs.rerun the same way before finishing. Report remaining Diagnostics or incomplete evidence exactly. If only shell execution is available, commands contains quoted POSIX command templates; replace placeholders with correctly quoted literal arguments before running them.
Use the Diagnostic Reference URL when the inline remediation is ambiguous or framework behavior needs confirmation. Routine fixes should not require network access.

Rules

Use vite-doctor for Vite, Vue, Nitro, and Nuxt projects; do not invent framework-specific packages or binaries.
Treat Rule IDs as execution/filtering selectors.
Treat Diagnostic Codes as the stable remediation identity for docs, fixes, and user-facing explanations.
Diagnostic Codes with non-built-in prefixes (anything other than DOC, NITRO, NUXT, PKG, SHAD, TS, VITE, VUE) come from Doctor Extensions shipped by libraries or the project. Use the docs URL in the Diagnostic; do not look for them in the Doctor Diagnostic Reference.
In Nuxt projects, Nuxt modules can register Doctor Extensions. nuxt doctor loads them; with the direct CLI, add --host-extensions to see the same Diagnostics. Keep that flag in commandArgs reruns.
To write or test custom Rules, follow https://vite-doctor.onmax.me/extending (vite-doctor/extension, vite-doctor/testkit).
When you will run Doctor several times in one project, set VITE_DOCTOR_SERVER=1 for those commands. Later runs reuse a long-lived Doctor process and print the same report; vite-doctor server stop ends it.
Prefer --format agent for remediation work. Use JSON for full run metadata and SARIF for code-scanning integrations.
An explicit --format is deterministic. Do not depend on automatic runtime recognition in scripts.
Use Doctor terms consistently: Doctor, Rule, Rule Pack, Diagnostic Code, and Diagnostic.
Keep code edits scoped to reported Diagnostics unless the user asks for broader cleanup.

doctor

Doctor

Quick Start