vercel-deploy

Vercel Deploy

Deploy any project to Vercel instantly. No authentication required.

How It Works

1. Packages your project into a .tar.gz (excludes node_modules and .git)
2. Auto-detects framework from package.json
3. Uploads to deployment service
4. Returns Preview URL (live site) and Claim URL (transfer to your Vercel account)

Usage

bash scripts/deploy.sh [path]

Arguments:

• path - Directory to deploy, or a .tgz file (defaults to current directory)

If you pass a directory, the script will create a .tar.gz before upload.

Examples:

# Deploy current directory
bash scripts/deploy.sh
 
# Deploy specific project
bash scripts/deploy.sh /path/to/project
 
# Deploy existing tarball
bash scripts/deploy.sh /path/to/project.tgz

Packaging Rules

• Exclude node_modules and .git
• If no package.json, keep framework as null
• For static HTML with a single .html file, rename it to index.html before packaging

Output

Preparing deployment...
Creating deployment package...

The script also outputs JSON to stdout for programmatic use.

Framework Detection

The script auto-detects frameworks from package.json. Supported frameworks include:

• React: Next.js, Gatsby, Create React App, Remix, React Router
• Vue: Nuxt, Vitepress, Vuepress, Gridsome
• Svelte: SvelteKit, Svelte, Sapper
• Other Frontend: Astro, Solid Start, Angular, Ember, Preact, Docusaurus
• Backend: Express, Hono, Fastify, NestJS, Elysia, h3, Nitro
• Build Tools: Vite, Parcel
• And more: Blitz, Hydrogen, RedwoodJS, Storybook, Sanity, etc.

For static HTML projects (no package.json), framework is set to null.

Static HTML Projects

For projects without a package.json:

• If there's a single .html file not named index.html, it gets renamed automatically
• This ensures the page is served at the root URL (/)

Present Results to User

Always show both URLs:

Troubleshooting

Network Egress Error

If deployment fails due to network restrictions, tell the user: