Vercel deployment

Set the Vercel Root Directory to docs for every standard documentation site. This is the consistent ownership boundary.

Workspace package is missing

A docs app can import packages from its parent workspace. The Vercel command must install from the workspace root and build required local packages before Nuxt builds docs. Keep Root Directory at docs; fix the command or dependency graph instead.

Test from a clean checkout without local dist/, .nuxt/, or node_modules/.

Corepack is unavailable

Vercel can require ENABLE_EXPERIMENTAL_COREPACK=1 for an older project image or configuration. Prefer a current runtime that supports the repository's packageManager field and an explicit install command. Use the environment flag only when current Vercel behavior requires it. Do not copy it to every project without evidence.

Generated Nuxt config is missing

If .nuxt/tsconfig.json is missing, ensure nuxt prepare runs before type-checking. Delete only generated .nuxt state when diagnosing stale output. Do not remove the required Vercel check.

Domain fails after a green build

Confirm the production deployment, domain assignment, DNS, and protection settings. A preview can be green while the canonical domain points to an old, protected, or failed deployment.