Skills Development Vercel Serverless Deployment Quick Start Guide

Vercel Serverless Deployment Quick Start Guide

v20260423
vercel-hello-world
This comprehensive guide provides a step-by-step walkthrough for deploying a minimal, functional full-stack application to Vercel. It covers setting up both static HTML landing pages and robust serverless API routes using TypeScript. This skill is ideal for beginners starting new Vercel projects, testing deployment pipelines, or learning the core patterns of modern serverless function implementation.
Get Skill
96 downloads
Overview

Vercel Hello World

Overview

Deploy a minimal project to Vercel with a static page and a serverless API route. Confirms your CLI auth, project structure, and deployment pipeline work end to end.

Prerequisites

  • Completed vercel-install-auth setup
  • Vercel CLI installed and authenticated
  • Node.js 18+

Instructions

Step 1: Create Project Structure

mkdir my-vercel-app && cd my-vercel-app
npm init -y

Create the static landing page:

<!-- public/index.html -->
<!DOCTYPE html>
<html>
<head><title>Hello Vercel</title></head>
<body>
  <h1>Hello from Vercel</h1>
  <p id="result">Loading...</p>
  <script>
    fetch('/api/hello')
      .then(r => r.json())
      .then(d => document.getElementById('result').textContent = d.message);
  </script>
</body>
</html>

Step 2: Create Serverless API Route

// api/hello.ts
import type { VercelRequest, VercelResponse } from '@vercel/node';

export default function handler(req: VercelRequest, res: VercelResponse) {
  res.status(200).json({
    message: 'Hello from Vercel Serverless Function!',
    timestamp: new Date().toISOString(),
    region: process.env.VERCEL_REGION || 'local',
  });
}

Install the types:

npm install --save-dev @vercel/node typescript

Step 3: Add vercel.json Configuration

{
  "rewrites": [
    { "source": "/api/(.*)", "destination": "/api/$1" }
  ],
  "headers": [
    {
      "source": "/api/(.*)",
      "headers": [
        { "key": "Cache-Control", "value": "s-maxage=0, stale-while-revalidate" }
      ]
    }
  ]
}

Step 4: Deploy Preview

# Deploy to a preview URL (not production)
vercel

# Output:
# Vercel CLI 39.x.x
# ๐Ÿ”— Linked to your-team/my-vercel-app
# ๐Ÿ” Inspect: https://vercel.com/your-team/my-vercel-app/xxx
# โœ… Preview: https://my-vercel-app-xxx.vercel.app

Step 5: Test the Deployment

# Test static page
curl -s https://my-vercel-app-xxx.vercel.app/ | head -5

# Test API route
curl -s https://my-vercel-app-xxx.vercel.app/api/hello | jq .
# {
#   "message": "Hello from Vercel Serverless Function!",
#   "timestamp": "2026-03-22T12:00:00.000Z",
#   "region": "iad1"
# }

Step 6: Promote to Production

# Deploy directly to production
vercel --prod

# Or promote the preview deployment
vercel promote https://my-vercel-app-xxx.vercel.app

Vercel System Environment Variables

These are available in every function at runtime:

VariableValue
VERCEL"1" โ€” always set on Vercel
VERCEL_ENV"production", "preview", or "development"
VERCEL_URLDeployment URL (no protocol)
VERCEL_REGIONFunction region (e.g., iad1)
VERCEL_GIT_COMMIT_SHAGit commit hash
VERCEL_GIT_COMMIT_MESSAGEGit commit message

Output

  • Static page served from Vercel CDN
  • Serverless API route returning JSON at /api/hello
  • Preview URL for testing before production
  • Production deployment live on your domain

Error Handling

ErrorCauseSolution
404 NOT_FOUND on /api/helloFile not in api/ directoryMove file to project root api/ folder
FUNCTION_INVOCATION_FAILEDRuntime error in handlerCheck function logs: vercel logs <url>
BUILD_FAILEDTypeScript compilation errorRun npx tsc --noEmit locally first
NO_RESPONSE_FROM_FUNCTIONHandler didn't call res.send/jsonEnsure all code paths return a response
FUNCTION_PAYLOAD_TOO_LARGEResponse body > 4.5 MBPaginate or stream the response

Resources

Next Steps

Proceed to vercel-local-dev-loop for development workflow setup.

Info
Category Development
Name vercel-hello-world
Version v20260423
Size 4.52KB
Updated At 2026-04-28
Language