vercel-deploy

Run the bundled deploy script with your project path: bash scripts/deploy.sh [path]. It packages the directory, uploads it to a claimable deploy endpoint, and returns a live Preview URL plus a Claim URL you can use later to transfer the deployment to a Vercel account.

The deploy script scans package.json dependencies in priority order, matching packages like next, nuxt, @sveltejs/kit, astro, express, and vite to their Vercel framework identifiers. If no package.json exists, the framework is set to null and the project is treated as static HTML.

Yes, projects without a package.json are deployed as static sites with the framework set to null. If the folder contains a single HTML file not named index.html, the script renames it to index.html so it serves at the root URL.

The packaging step excludes node_modules, .git, and .env files including .env.* variants. Files are staged into a temporary directory before creating the .tar.gz archive, so the source tree is never modified.

Deployment fails with timeouts, DNS errors, or connection resets when sandbox networking blocks outbound requests to the deploy endpoint. Rerun the deploy command with escalated permissions using sandbox_permissions=require_escalated to allow the network calls.