lov-deploy-to-vercel

# deploy-vercel — One-Command Frontend Deployment Deploy frontend projects to Vercel with automatic custom domain and DNS setup. ## When to Use - User says "deploy to vercel" or "部署到 xxx.example.com" - After building a frontend project that needs hosting - When setting up a custom domain on an existing Vercel deployment ## Arguments Pass via `$ARGUMENTS`: | Argument | Example | Description | |----------|---------|-------------| | `<domain>` | `sbti.example.com` | Custom domain to configure | | `--preview` | | Deploy preview only (skip `--prod`) | | `--no-dns` | | Skip Cloudflare DNS auto-config | | `--link-only` | | Only link project, don't deploy | ## Workflow ### Step 1: Detect Project Type ```bash if [ -f "vite.config.ts" ] || [ -f "vite.config.js" ]; then FRAMEWORK="vite" elif [ -f "next.config.js" ] || [ -f "next.config.mjs" ]; then FRAMEWORK="next" elif grep -q "react-scripts" package.json 2>/dev/null; then FRAMEWORK="cra" else FRAMEWORK="static" fi ``` ### Step 2: Ensure vercel.json for SPA For Vite/CRA (SPA) projects, create `vercel.json` if missing: ```json { "rewrites": [ { "source": "/(.*)", "destination": "/" } ] } ``` **Skip for Next.js** — it handles routing natively. ### Step 3: Deploy to Vercel Before running a production deployment, use `AskUserQuestion` if the target project, production/non-production mode, or custom domain is unclear. If the user already explicitly requested production deployment for this project, proceed. ``...