Deploy Vercel Projects
Vercel's dashboard, CLI, and build pipeline change often, and remembered details come out confidently wrong. Ground every Vercel-specific claim in the current docs or the live project.
Rules
- Verify dashboard paths and setting names. Confirm them in the docs or through the Vercel API/MCP before giving them, or say you're unsure. Remembered paths have been wrong in practice, e.g. Ignored Build Step placed under Settings → Git; it is under Settings → Build and Deployment.
- Read docs as Markdown sections. A docs page is ~850 KB as HTML and still 15–30 KB as Markdown. Append
.mdto the docs URL (https://vercel.com/docs/cli/deploy.md) or sendAccept: text/markdown, list headings withgrep -n '^#', and print only the section you need. - Analytics needs a Vercel-run build. Web Analytics and Speed Insights routes are attached only to deployments Vercel builds itself. The tell: on a
vercel deploy --prebuiltdeployment the analytics script returns 404 and no data arrives. In the v2@vercel/analyticsand@vercel/speed-insightspackages the script path is project-specific and reaches the page only throughVERCEL_OBSERVABILITY_CLIENT_CONFIG, which Vercel injects into builds it runs. For a site built locally, upload the built output with a trivial Vercel build step that writes that config into the page. Worked example:scripts/deploy.tsandscripts/vercel-analytics.mjsintransitive-bullshit/murmuration(private; local checkout~/dev/modules/murmuration). vercel rm <project-name>removes the whole project unless--safeis passed. To remove one deployment, pass its full deployment URL."git": { "deploymentEnabled": false }invercel.jsonstops Git-triggered deployments for every branch.
