vercel-deploy

To deploy to Vercel, run the deployment bash script with your project path. It auto-packages the directory, invokes a remote endpoint, and returns a JSON payload containing the previewUrl, claimUrl, deploymentId, and projectId.

Vercel deployment framework auto-detection reads your project's package.json to identify the framework and ensure correct build behavior. For static HTML projects lacking a package.json, it renames a root HTML file to index.html to enable proper hosting.

Yes, you can deploy an existing tarball to Vercel by passing the .tgz file path directly to the deployment script. The script also accepts project directories and automatically excludes node_modules and .git folders during packaging.

No, you do not need to manually exclude node_modules when packaging for Vercel deployment. The deployment script automatically filters out node_modules and .git directories from the project tarball before invoking the remote endpoint.

A Vercel Claim URL is a transferable deployment link returned after deploying a project. It allows stakeholders to view the live preview and transfer the deployment directly into their own Vercel account for production management.

To handle Vercel deployment for static HTML sites without package.json, the deployment script automatically renames a root HTML file to index.html. This ensures proper static hosting behavior on the Vercel platform.