vercel-debug-bundle

# Vercel Debug Bundle ## Overview Collect a comprehensive debug bundle containing deployment state, function logs, environment configuration, and build output for Vercel support escalation or team troubleshooting. ## Current State !`vercel --version 2>/dev/null || echo 'Vercel CLI not installed'` !`node --version 2>/dev/null || echo 'Node.js N/A'` ## Prerequisites - Vercel CLI installed and authenticated - Access to the affected deployment - `jq` for JSON processing (recommended) ## Instructions ### Step 1: Collect Deployment Information ```bash #!/usr/bin/env bash set -euo pipefail DEPLOY_URL="${1:-$(vercel ls --json 2>/dev/null | jq -r '.[0].url')}" BUNDLE_DIR="vercel-debug-$(date +%Y%m%d-%H%M%S)" mkdir -p "$BUNDLE_DIR" echo "=== Collecting debug bundle for: $DEPLOY_URL ===" # Deployment inspection vercel inspect "$DEPLOY_URL" > "$BUNDLE_DIR/inspect.txt" 2>&1 || true # Deployment details via API curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \ "https://api.vercel.com/v13/deployments/$DEPLOY_URL" \ | jq '{uid, name, state, target, readyState, errorMessage, meta, regions}' \ > "$BUNDLE_DIR/deployment.json" 2>/dev/null || true ``` ### Step 2: Collect Function Logs ```bash # Recent function logs (last 100 entries) vercel logs "$DEPLOY_URL" --output=short --limit=100 \ > "$BUNDLE_DIR/function-logs.txt" 2>&1 || true # Function logs via API with filtering curl -s -H "Authorization: Bearer $VERCEL_TOKEN" \ "https://api.vercel.com/v2/deployments/$DEPLOY_URL/ev...