vercel-cli

# Vercel CLI You can deploy web applications to Vercel using the `vercel` CLI. ## Auth Auth is handled by OneCLI — the HTTPS_PROXY injects the real token into API requests automatically. The Vercel CLI requires a token to be present to skip its local credential check, so **always pass `--token placeholder`** on every command. OneCLI replaces this with the real token at the proxy level. Before any Vercel operation, verify auth: ```bash vercel whoami --token placeholder ``` If this fails with an auth error, ask the user to add a Vercel token to OneCLI. They can create one at https://vercel.com/account/tokens and register it via `onecli secrets create` on the host. Once added, retry `vercel whoami`. ## Deploying Always use `--yes` to skip interactive prompts and `--token placeholder` for auth (OneCLI replaces with real token). ```bash # Deploy to production vercel deploy --yes --prod --token placeholder # Deploy from a specific directory vercel deploy --yes --prod --token placeholder --cwd /path/to/project # Preview deployment (not production) vercel deploy --yes --token placeholder ``` After deploying, verify the live URL: ```bash # Check deployment status vercel inspect <deployment-url> --token placeholder ``` ## Pre-Send Checks (do this before sharing the URL) Don't send the deployment URL to the user until you've confirmed it's actually working. At minimum: 1. **Local build passes** — run `npm run build` (or the project's build command) before `vercel deploy`...