Vercel

Use this page to find package-specific Vercel guidance in ViteHub.

Currently documented packages

KV

@vitehub/kv supports a Vercel path through the Upstash-backed upstash driver.

• Setup overview: KV overview
• Provider details: KV on Vercel

DB

@vitehub/db supports Vercel on Vite through hosted libSQL connections, including optional named databases behind the same runtime surface.

• Setup overview: DB overview
• Provider details: DB on Vercel

Blob

@vitehub/blob supports a Vercel path on Vite and Nitro through the vercel-blob driver.

• Setup overview: Blob overview
• Provider details: Blob on Vercel

Queue

@vitehub/queue supports a Vercel path on Vite and Nitro through queue.provider = 'vercel'.

• Setup overview: Queue overview
• Provider details: Queue on Vercel

Schedule

@vitehub/schedule supports Vercel Provider Output on Vite and Nitro when the Vite Integration or Nitro Integration discovers Static Schedule Definitions.

• Setup overview: Schedule overview
• Provider details: ViteHub writes Vercel cron entries to .vercel/output/config.json and generated functions under /api/vitehub/schedules/vercel/<name> during the manual deploy build.

What stays package-specific

Environment variables, fallback behavior, and exact config examples live with the package docs. Use this section as a routing page, not as the source of truth for package setup.

Schedule Runtime Helpers are separate from Provider Output. Creating or changing a Runtime Schedule does not automatically provision Vercel cron configuration; provider cron paths come from Static Schedule Definitions discovered at build time.