Build & Function Logs

WebStadia provides real-time logs for both build processes and serverless function execution.

Build Logs

Every deployment generates build logs you can view in real time from the Hosting tab.

Build logs show:

• Framework detection
• Dependency installation (npm install)
• Build output (npm run build)
• Asset upload progress
• Deployment status

Viewing Build Logs

1. Go to your website's Hosting page
2. During an active build, the build progress panel shows live logs
3. For past builds, go to Deployments to see build history

Common Build Failures

Error	Cause	Fix
command not found: vite	Dev dependencies not installed	Remove NODE_ENV=production from env vars
ENOENT: package.json	Wrong root directory	Set Root Directory in build settings
Module not found	Missing dependency	Check package.json dependencies
Lint warnings treated as errors	CI=true makes warnings fatal	WebStadia sets CI=false by default
out of memory	Build exceeds container memory	Reduce bundle size or upgrade plan

Function Logs

For serverless apps (Express, Next.js SSR, Fastify, etc.), function logs capture runtime output from your server code.

Accessing Function Logs

1. Go to your website in the dashboard
2. Click Logs in the sidebar
3. Logs show all console.log, console.error, and framework output

Log Features

• Live mode — auto-refreshes every 10 seconds with a green pulse indicator
• Time range — filter from last 15 minutes to last 7 days
• Level filter — show only errors, warnings, info, or system messages
• Search — filter by keyword, request ID, or path
• Load more — paginate through older logs

Log Levels

Level	Color	Description
Error	Red	Unhandled exceptions, crash logs
Warning	Yellow	Cold starts, deprecation notices
Info	Gray	console.log output, request logs
System	Blue	START/END/REPORT lines per request

Understanding System Logs

Each function invocation produces three system lines:

START RequestId: abc-123
// ... your console.log output ...
END RequestId: abc-123
REPORT RequestId: abc-123  Duration: 45.2 ms  Memory: 128/256 MB

The REPORT line shows:

• Duration — how long your code ran
• Billed Duration — rounded up to nearest ms
• Memory Used / Memory Size — peak memory vs allocated
• Init Duration — cold start time (only on first invocation)

Cold Starts

A cold start occurs when your function hasn't been invoked recently. The first request takes longer because the runtime needs to initialize.

Tips to reduce cold starts:

• Keep your deployment package small
• Minimize top-level imports
• Use Next.js standalone mode (enabled automatically)

Log Retention

Logs are retained based on your plan:

• Free: 1 day
• Personal: 3 days
• Agency: 7 days
• Agency Plus: 14 days
• Enterprise: 30 days